CVE-2024-6844: Inconsistent CORS Matching Due to Handling of '+' in URL Path in corydolphin/flask-cors
A vulnerability in corydolphin/flask-cors version 4.0.1 allows for inconsistent CORS matching due to the handling of the '+' character in URL paths. The request.path is passed through the unquoteplus function, which converts the '+' character to a space ' '. This behavior leads to incorrect path normalization, causing potential mismatches in CORS configuration. As a result, endpoints may not be matched correctly to their CORS settings, leading to unexpected CORS policy application. This can cause unauthorized cross-origin access or block valid requests, creating security vulnerabilities and usability issues.
Other sources
A vulnerability in corydolphin/flask-cors version 5.0.1 allows for inconsistent CORS matching due to the handling of the '+' character in URL paths. The request.path is passed through the unquoteplus function, which converts the '+' character to a space ' '. This behavior leads to incorrect path normalization, causing potential mismatches in CORS configuration. As a result, endpoints may not be matched correctly to their CORS settings, leading to unexpected CORS policy application. This can cause unauthorized cross-origin access or block valid requests, creating security vulnerabilities and usability issues.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-6844?
CVE-2024-6844 has been classified as a moderate severity vulnerability due to potential issues with CORS matching.
How do I fix CVE-2024-6844?
To fix CVE-2024-6844, upgrade to version 4.0.2 or later of flask-cors where the inconsistency in CORS matching has been addressed.
Which software versions are affected by CVE-2024-6844?
CVE-2024-6844 affects flask-cors version 4.0.1.
What kind of issues does CVE-2024-6844 create?
CVE-2024-6844 creates issues with inconsistent CORS behavior that can lead to security vulnerabilities when handling requests.
Is there a known exploit for CVE-2024-6844?
As of now, there are no publicly known exploits for CVE-2024-6844, but it poses a risk that should not be ignored.