This repository has been archived by the owner on Oct 2, 2024. It is now read-only.
Update express to 4.17.3 to address querystring vulnerability #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See GLOB-70859 and https://github.com/n8tz/CVE-2022-24999 for background on this vulnerability.
I managed to reproduce the exploit by borrowing from the vulnerability repo's POC in globalitydocx. I added a dummy route that looked like this:
Then sent a request to a locally-running server with this:
Without the update to this library, the server treated
categories
like an array and took 4 seconds to respond (even if its own copy of express was updated to the fix version). Once I got the local server to use this version of nodule-express, it responded to the same request quickly, and hit theCategories is not an array
branch.