CVE-2024-1681Medium· 5.3▾ Sunlitflask-cors vulnerable to log injection when the log level is set to debug
▾ 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 Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.6%
corydolphin/flask-cors is vulnerable to log injection when the log level is set to debug. An attacker can inject fake log entries into the log file by sending a specially crafted GET request containing a CRLF sequence in the request path. This vulnerability allows attackers to corrupt log files, potentially covering tracks of other attacks, confusing log post-processing tools, and forging log entries. The issue is due to improper output neutralization for logs.
flask-cors < 4.0.1Upgrade to a patched release:
flask-cors 4.0.1Connected by shared product, vendor, weakness, or advisory.
CVE-2024-6844Medium· 5.3Flask-CORS allows for inconsistent CORS matching
CVE-2024-6839Medium· 4.3Flask-CORS improper regex path matching vulnerability
CVE-2024-6866Medium· 5.3Flask-CORS vulnerable to Improper Handling of Case Sensitivity
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