-
Notifications
You must be signed in to change notification settings - Fork 4
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
Preserve path traversal vulnerability #142
Labels
Comments
derevnjuk
added a commit
that referenced
this issue
Jun 5, 2023
derevnjuk
added a commit
that referenced
this issue
Jun 5, 2023
derevnjuk
added a commit
that referenced
this issue
Jun 5, 2023
derevnjuk
added a commit
that referenced
this issue
Jun 5, 2023
derevnjuk
added a commit
that referenced
this issue
Jun 5, 2023
derevnjuk
added a commit
that referenced
this issue
Jun 5, 2023
derevnjuk
added a commit
that referenced
this issue
Jun 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current implementation of URL parsing and validation in the application does not allow to detect the directory traversal vulnerability. The application is using the secure WHATWG API instead of the less secure
url.parse()
.Steps to Reproduce:
http://192.168.0.161:3000/public/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd
http://192.168.0.161:3000/public/../../../../../../etc/passwd
Expected Result:
The application should send a request by the following
/public/../../../../../../etc/passwd
paht. The resulting URL should allow access to sensitive files outside the intended directory.Actual Result:
The application does not allow directory traversal attacks. As a result, the parsed URL is
http://192.168.0.161:3000/etc/passwd
.The text was updated successfully, but these errors were encountered: