CVE-2020-5207: Request smuggling is possible in Ktor when both chunked TE and content length specified
First published: Mon Jan 27 2020(Updated: )
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.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| JetBrains Ktor | <1.3.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2020-5207?
CVE-2020-5207 is a vulnerability in Ktor before version 1.3.0 that allows request smuggling when running behind a proxy that doesn't handle Content-Length and Transfer-Encoding properly or doesn't handle \n as a headers separator.
What is the severity of CVE-2020-5207?
The severity of CVE-2020-5207 is high, with a severity score of 7.5.
Which software is affected by CVE-2020-5207?
The affected software is JetBrains Ktor up to version 1.3.0.
How can I fix CVE-2020-5207?
To fix CVE-2020-5207, update your Ktor installation to version 1.3.0 or higher.
Where can I find more information about CVE-2020-5207?
You can find more information about CVE-2020-5207 in the security advisory published by JetBrains Ktor: [link].
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/remedy
- agent/weakness
- agent/author
- agent/title
- agent/description
- agent/tags
- agent/event
- agent/first-publish-date
- vendor/jetbrains
- canonical/jetbrains ktor