Skip to content

JS: Block XSS flow through encodeURIComponent#2216

Merged
semmle-qlci merged 1 commit intogithub:masterfrom
asger-semmle:xss-encodeURIComponent
Oct 30, 2019
Merged

JS: Block XSS flow through encodeURIComponent#2216
semmle-qlci merged 1 commit intogithub:masterfrom
asger-semmle:xss-encodeURIComponent

Conversation

@asger-semmle
Copy link
Copy Markdown
Contributor

Strawman solution to #2196. Haven't run an evaluation yet as we're a bit low on machines.

@asger-semmle asger-semmle requested a review from a team as a code owner October 28, 2019 17:15
Copy link
Copy Markdown
Contributor

@max-schaefer max-schaefer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I think that's a fine solution for now. Needs a change note, though.

@asger-semmle
Copy link
Copy Markdown
Contributor Author

Evaluation looks fine. We lose one result which looks like a FP anyway.

@asger-semmle
Copy link
Copy Markdown
Contributor Author

I believe it's already covered by the existing change note:

| Client-side cross-site scripting (js/xss) | More results, fewer false-positive results | More potential vulnerabilities involving functions that manipulate DOM attributes are now recognized, and more sanitizers are detected. |

@semmle-qlci semmle-qlci merged commit a778efe into github:master Oct 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants