-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
JS: Add support for escape
#19027
JS: Add support for escape
#19027
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds support for handling the escape and unescape functions in test cases for tainted paths.
- Added test cases in TaintedPath.js to validate flows involving escape() and unescape()
- Updated change notes to document the new flow steps
Reviewed Changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.
File | Description |
---|---|
javascript/ql/test/query-tests/Security/CWE-022/TaintedPath/TaintedPath.js | Added test cases using escape() and unescape() to trigger security alerts |
javascript/ql/lib/change-notes/2025-03-14-escape.md | Documented the support added for escape() and unescape() flows |
Files not reviewed (2)
- javascript/ql/lib/semmle/javascript/security/dataflow/TaintedPathCustomizations.qll: Language not supported
- javascript/ql/test/query-tests/Security/CWE-022/TaintedPath/TaintedPath.expected: Language not supported
Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more
Could you also add You can look at |
javascript/ql/lib/semmle/javascript/security/dataflow/TaintedPathCustomizations.qll
Outdated
Show resolved
Hide resolved
…athCustomizations.qll Co-authored-by: Asger F <asgerf@github.com>
Included
escape
andunescape
functions as additional flow steps.