CVE-2020-5207GHSA-XRR9-RH8P-433V
Request smuggling is possible in Ktor when both chunked TE and content length specified
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.3.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Ktor.io Ktor
fixed in 1.3.0
- io.ktor:ktor-client-cioMaven
fixed in 1.3.0
- io.ktor:ktor-server-cioMaven
fixed in 1.3.0