Flask Cors
Approved changes feed: RSS · Atom
cpe:2.3:a:corydolphin:flask-cors:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Corydolphin (f1137166-1dca-501c-89c0-ee3978877ce2) |
|---|---|
| Product | Flask Cors (4f2d9ea2-fd78-5313-a15b-02da4ba9500b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-1681 |
vulnerable | 2026-06-08 06:27:14.072594 |
Log Injection Vulnerability in corydolphin/flask-cors
MEDIUM (5.3)
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.
Published: 2024-04-19T19:37:27.998Z
Updated: 2025-11-03T19:29:18.706Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.