CVE-2020-5207
Request smuggling is possible in Ktor when both chunked TE and content length specified
Vexday Risk Score
13Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS 5.4EPSS 0.8%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
27 Jan 2020Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Affected products
Ktor.io · KtorWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →