CVE-2024-6866: Case-Insensitive Path Matching in corydolphin/flask-cors
corydolphin/flask-cors version 4.01 contains a vulnerability where the request path matching is case-insensitive due to the use of the trymatch function, which is originally intended for matching hosts. This results in a mismatch because paths in URLs are case-sensitive, but the regex matching treats them as case-insensitive. This misconfiguration can lead to significant security vulnerabilities, allowing unauthorized origins to access paths meant to be restricted, resulting in data exposure and potential data leaks.
Other sources
corydolphin/flask-cors version 5.0.1 contains a vulnerability where the request path matching is case-insensitive due to the use of the trymatch function, which is originally intended for matching hosts. This results in a mismatch because paths in URLs are case-sensitive, but the regex matching treats them as case-insensitive. This misconfiguration can lead to significant security vulnerabilities, allowing unauthorized origins to access paths meant to be restricted, resulting in data exposure and potential data leaks.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-6866?
CVE-2024-6866 has been assigned a medium severity rating due to the potential for path manipulation.
How do I fix CVE-2024-6866?
To fix CVE-2024-6866, update the flask-cors package to a version where the request path matching is case-sensitive.
What software versions are affected by CVE-2024-6866?
CVE-2024-6866 affects version 4.01 of the flask-cors library by corydolphin.
What types of attacks can exploit CVE-2024-6866?
CVE-2024-6866 can potentially be exploited for path traversal or bypassing security controls due to improper case matching.
Has CVE-2024-6866 been reported in any public security advisories?
Yes, CVE-2024-6866 is documented in public security advisories and vulnerability databases.