Fix CORS vulnerability by replacing wildcard '*' with configurable and restricted origins. #994
Add this suggestion to a batch that can b
2FEA
e 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.
Summary
Pull Request Summary:
The Vulnerability Description:
Previously, the CORS policy allowed requests from any origin using a wildcard ('*'). This made the application vulnerable to cross-origin attacks as it failed to restrict access to trusted domains.
This Fix:
Modified the CORS settings to limit allowed origins based on configuration values (
TRACECAT__ALLOW_ORIGINS
) or the default public app URL (TRACECAT__PUBLIC_APP_URL
). This ensures that only trusted origins can interact with the application.The Cause of the Issue:
The usage of the wildcard ('*') in the CORS policy meant unrestricted access was granted to all origins. This created a security risk by allowing untrusted domains to potentially exploit the API's functionality.
The Patch Implementation:
Introduced a conditional logic to derive
allow_origins
—if explicitly configured, it processes a list of origins fromTRACECAT__ALLOW_ORIGINS
. Otherwise, it defaults to the public app URL (TRACECAT__PUBLIC_APP_URL
). This removes the use of the wildcard and enforces origin validation.Vulnerability Details
Code Snippets
How to Modify the Patch
You can modify this patch by using one of the two methods outlined below. We recommend using the
@zeropath-ai
bot for updating the code. If you encounter any bugs or issues with the patch, please report them here.Ask
@zeropath-ai
!To request modifications, please post a comment beginning with
@zeropath-ai
and specify the changes required.@zeropath-ai
will then implement the requested adjustments and commit them to the specified branch in this pull request. Our bot is capable of managing changes across multiple files and various development-related requests.Manually Modify the Files