Fixed Cross-Origin Resource Sharing (CORS) configuration #7183
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR addresses a critical security vulnerability in Cross-Origin Resource Sharing (CORS) configuration by ensuring the Vary: Origin response header is set. The fix prevents potential exploitation of CORS misconfigurations by informing browsers that responses can vary based on the Origin request header.
Fix was done by:
Adding the Vary: Origin header to HttpServletResponse in the handleSimpleCORS method.
Ensuring the browser caches the response correctly based on the origin.
References
Related fix commit