CVE-2024-6866Medium· 5.3▾ SunlitFlask-CORS vulnerable to Improper Handling of Case Sensitivity
▾ Sunlit zone — Low / medium · no exploitation signal
impact 29.2 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
0.6%
Last analysed / modified upstream
0.6% → 0.7%
corydolphin/flask-cors version 5.0.1 contains a vulnerability where the request path matching is case-insensitive due to the use of the try_match 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.
flask-cors < 6.0.0Upgrade to a patched release:
flask-cors 6.0.0Connected by shared product, vendor, weakness, or advisory.
CVE-2024-1681Medium· 5.3flask-cors vulnerable to log injection when the log level is set to debug
CVE-2024-6844Medium· 5.3Flask-CORS allows for inconsistent CORS matching
CVE-2024-6839Medium· 4.3Flask-CORS improper regex path matching vulnerability
CVE-2020-25032High· 7.5Flask-Cors Directory Traversal vulnerability
CVE-2024-6221High· 7.5Flask-CORS allows the `Access-Control-Allow-Private-Network` CORS header to be set to true by default