Add exclusions for header injection vulnerability #4841
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.
What does this PR do?
Adds new exclusions for the header injection vulnerability in order to reduce false positives:
Transfer-Encoding/Content-Encoding
: when sources come fromAccept-Encoding
Pragma
: when sources come fromCache-Control
Motivation
Reduce false positives in header injection vulnerability detections
Additional Notes
Previously, the
set-cookie
header exclusion checked that the source of the range was both the value of a cookie and the name of a cookie. Since cookie names are not being tainted, this check has been removed.vary
header should be ignored if the tainted portion is composed only from request header names, but since header names are not being tainted, this check has not been implemented.APPSEC-55563