In Ktor before 1.3.0, request smuggling is possible when running behind a proxy that doesn't handle Content-Length and Transfer-Encoding properly or doesn't handle \n as a headers separator.
Loading...
Loading...
This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
In Ktor before 1.3.0, request smuggling is possible when running behind a proxy that doesn't handle Content-Length and Transfer-Encoding properly or doesn't handle \n as a headers separator.
January 27, 2020
November 21, 2024
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| io.ktor:ktor-client-cio | 1.0.0 ... 1.3.0-rc2 (21 versions) | 1.3.0 | — |
| io.ktor:ktor-server-cio | 1.0.0 ... 1.3.0-rc2 (20 versions) | 1.3.0 | — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-5207
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.