-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add context/path information to JSON-based string accesses #199
Comments
@vladidx would you also need the entire JSON content as an additional argument, or do you have this information from e.g. the XHR response? Adding the entire JSON string as an argument might be quite memory intensive... |
No, the JSON content is not needed |
I'm working on a fix for this which would give:
as the JSON Path for the above example. Would this be sufficient? |
Yes, that would be already sufficient, thanks. |
Ooops, just checked the spec again, I guess it should be a leading |
👍 |
This is implemented with #200 |
JSON objects are often created from XHR responses and then flowing into the DOM (potentially without escaping).
It would be quite helpful to know the path/context of the tainted string within the JSON object, e.g. as part of the arguments:
Ideally, the context information would be a kind of XPath for JSON as described here.
The text was updated successfully, but these errors were encountered: