Backwards Compatible Fix for CVE-2024-6221 #363
Merged
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.
Backwards Compatible Fix for CVE-2024-6221
Also tracked as:
Adds a configuration option that allows setting a custom true/false value in the response header
Access-Control-Allow-Private-Network
(whenever the request headerAccess-Control-Request-Private-Network
is present and"true"
)The default behavior is unchanged, allowing this change to go in as a new minor version.
However, the wording of the CVE implies that the default behavior should be changed to set the header to
"false"
unless setting to"true"
is explicitly enabled.Making that change means simply changing the
allow_private_network=True
toallow_private_network=False
in the options list. This would require cutting a new major version (5.0.0) forflask-cors
.