-
Notifications
You must be signed in to change notification settings - Fork 307
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
FISH-9690: adding new version of grizzly to validate headers RFC-9110 #7060
Open
breakponchito
wants to merge
1
commit into
payara:main
Choose a base branch
from
breakponchito:FISH-9690-filtering-incorrect-characters-rfc-9110
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
FISH-9690: adding new version of grizzly to validate headers RFC-9110 #7060
breakponchito
wants to merge
1
commit into
payara:main
from
breakponchito:FISH-9690-filtering-incorrect-characters-rfc-9110
Conversation
This file contains 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
this depend of the following PR: payara/patched-src-grizzly#39 |
Jenkins test please |
5 similar comments
Jenkins test please |
Jenkins test please |
Jenkins test please |
Jenkins test please |
Jenkins test please |
Jenkins test please |
Pandrex247
requested changes
Nov 22, 2024
@@ -617,6 +617,7 @@ | |||
<exclude>io.opentelemetry.extension</exclude> | |||
<exclude>io.opentelemetry.instrumentation</exclude> | |||
<exclude>fish.payara.shaded</exclude> | |||
<exclude>org.glassfish.grizzly.http</exclude> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't ever be adding anything to this.
Please rework the Grizzly change
Suggested change
<exclude>org.glassfish.grizzly.http</exclude> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding Header validation for RFC-9110
Description
This is a security fix to prevent issues based on CVE reported here:
[CVE-2024-45687](https://www.cve.org/CVERecord?id=CVE-2024-45687)
and here glassfish issueImportant Info
Blockers
Testing
New tests
Manual testing:
Testing Performed
To test this set the dependency version on the payara server: 4.0.2.payara-p2 build and run
deploy the following reproducer:
ReproducerJDK11.zip
after starting the server set the following properties on the Payara configuration. You can do it by console ui, command line or directly on the domain.xml file:
asadmin create-jvm-options --target=server-config "-Dorg.glassfish.grizzly.http.STRICT_HEADER_NAME_VALIDATION_RFC_9110\=true"
asadmin create-jvm-options --target=server-config "-Dorg.glassfish.grizzly.http.STRICT_HEADER_VALUE_VALIDATION_RFC_9110\=true"
after adding the properties you need to restart the server
by default on the grizzly side those properties are set as false
deploy the reproducer and make curl calls
Header Name Validation tests:
the result of any of those test should be error 400:
Header Value Validations tests:
In the case of header validation we can't be very strict on the validation that is why the \n is permitted an is evaluated as a new line on the content for the header value and the \0 is immediately not processed from curl because by default we can't consider that character on the request headers and the \r character can be included as a character on the header values and this will be rejected
Testing Environment
Windows 11, Azul jdk 11, maven 3.9.5
Documentation
working on documentation
Notes for Reviewers