CVE-2020-7695 Details
Description
Uvicorn before 0.11.7 is vulnerable to HTTP response splitting. CRLF sequences are not escaped in the value of HTTP headers. Attackers can exploit this to add arbitrary headers to HTTP responses, or even return an arbitrary response body, whenever crafted input is used to construct HTTP headers.
A vulnerability allowing HTTP response splitting has been identified in Uvicorn versions prior to 0.11.7. This issue arises because CRLF sequences are not properly escaped in HTTP header values. As a result, attackers can exploit this flaw to inject arbitrary headers into HTTP responses or even return custom response bodies, whenever crafted input is used to create HTTP headers.
Upgrade Uvicorn to version 0.11.7 or higher.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/encode/uvicorn | CVE | Third Party Advisory |
| https://snyk.io/vuln/SNYK-PYTHON-UVICORN-570471 | CVE | ExploitThird Party Advisory |
| https://github.com/encode/uvicorn | [email protected] | Third Party Advisory |
| https://snyk.io/vuln/SNYK-PYTHON-UVICORN-570471 | [email protected] | ExploitThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-74 | Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| encode uvicorn | < 0.11.7 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| Jan 31, 2023 | Modified Analysis | [email protected] |
| Jul 29, 2020 | CVE Modified | [email protected] |
| Jul 29, 2020 | Initial Analysis | [email protected] |