Fix region Type confusion through parameter tampering #33301
+4
−0
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.
react/fixtures/flight-esm/server/region.js
Line 180 in 73f06e0
To fix the issue, we need to ensure that
req.query.name
is explicitly validated to be a string before it is used. If it is not a string, the code should handle the case appropriately, such as returning an error response. This can be achieved by adding a type check forreq.query.name
and rejecting the request if it is not a string.The changes will be made in the
/source-maps
route handler:req.query.name
to ensure it is a string.req.query.name
is not a string, return a400 Bad Request
response with an appropriate error message.References
querystring
CWE-843