-
Notifications
You must be signed in to change notification settings - Fork 18
Block request if URL path contains path traversal patterns #599
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
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! |
| } | ||
|
|
||
| // Also check encoded paths | ||
| const decodedPath = decodeURIComponent(rawPath); |
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.
Does not cover double-encoding, should we?
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.
Question for @kapyteinaikido
Extracted from #595 Co-Authored-By: Hans Ott <[email protected]>
library/vulnerabilities/path-traversal/checkUrlPathForPathTraversal.ts
Outdated
Show resolved
Hide resolved
| return true; | ||
| } | ||
|
|
||
| // Only checks the url path for path traversal attacks, other inputs are checked using the sinks |
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.
Function handles multiple unrelated security concerns (IP blocking, user agent blocking, path traversal) in 185 lines.
Feedback
Post a comment with the following structure to provide feedback on this finding:
@AikidoSec feedback: [FEEDBACK]
Aikido will process this feedback into learnings to give better review comments in the future.
More info
No description provided.