Improper Output Neutralization for Logs Affecting python-flask-cors package, versions <4.0.1-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Output Neutralization for Logs vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-DEBIAN13-PYTHONFLASKCORS-6672287
- published23 Apr 2024
- disclosed19 Apr 2024
Introduced: 19 Apr 2024
CVE-2024-1681 (opens in a new tab)How to fix?
Upgrade Debian:13 python-flask-cors to version 4.0.1-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream python-flask-cors package and not the python-flask-cors package as distributed by Debian.
See How to fix? for Debian:13 relevant fixed versions and status.
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.