[🍒][PLUGIN-1934]: Fix CVEs in jetty-http 9.4.12.v20180830 #349
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Krish-cloudsufi
changed the title
|
LGTM. |
Contributor
MrRahulSharma
left a comment
MrRahulSharma
left a comment
There was a problem hiding this comment.
Can you add details in the description about the validations performed with this change ?
Contributor
Author
Added details of the validations performed, including Pipeline run link and CVE verification link, in the description. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
[🍒]
🍒 [cherrypick]
Commits:
PR:
Description:
PLUGIN-1934: This PR upgrades the Jetty HTTP dependency to address an issue where Jetty accepted a '+' character preceding the Content-Length value in HTTP/1 headers. This behavior was more permissive than allowed by the RFC and could potentially lead to HTTP request smuggling when Jetty is used alongside servers that strictly validate such headers (e.g., NGINX, Apache).
Fix: Upgraded the Jetty HTTP dependency from version 9.4.12.v20180830 to 9.4.52.v20230823, where strict validation of the Content-Length header is enforced and the issue is resolved.
CVE Fix Verification: https://screenshot.googleplex.com/7RjXpjeSc7rx4zr
Pipeline Run: https://screenshot.googleplex.com/AcYid2CdAbnhkeK
JIRA: PLUGIN-1934