Log forgery via unescaped request paths
Published Apr 19, 2024 · Updated Nov 3, 2025
Log injection in Cory Dolphin Flask-CORS 4.0.0 and earlier allows remote attackers to forge log entries through crafted request paths. The cors_after_request function logs request.path with the %s formatter, so decoded CRLF characters reach the debug log without neutralization. Exposure requires Flask-CORS debug logging and a reachable Flask route; injected lines can corrupt audit trails and mislead log-processing tools.
Summary
What happened
Log injection in Cory Dolphin Flask-CORS 4.0.0 and earlier allows remote attackers to forge log entries through crafted request paths. The cors_after_request function logs request.path with the %s formatter, so decoded CRLF characters reach the debug log without neutralization. Exposure requires Flask-CORS debug logging and a reachable Flask route; injected lines can corrupt audit trails and mislead log-processing tools.
The record
- CVE
- CVE-2024-1681
- Published
- Apr 19, 2024
- Updated
- Nov 3, 2025
- Vendor
- Cory Dolphin
- Product
- Flask-CORS
- Classifications
- CWE-117, CAPEC-81, CAPEC-268, CAPEC-93, T1070
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 19, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=-
- Affected versionversion=unspecified <=latest
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Huntr CRLF log-injection submissionproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo