# |
CVE ID
|
CWE ID
|
# of Exploits
|
Vulnerability Type(s)
|
Publish Date
|
Update Date
|
Score
|
Gained Access Level
|
Access
|
Complexity
|
Authentication
|
Conf.
|
Integ.
|
Avail.
|
1 |
CVE-2020-15811 |
444 |
|
Http R.Spl. Bypass |
2020-09-02 |
2021-03-04 |
4.0 |
None |
Remote |
Low |
??? |
None |
Partial |
None |
An issue was discovered in Squid before 4.13 and 5.x before 5.0.4. Due to incorrect data validation, HTTP Request Splitting attacks may succeed against HTTP and HTTPS traffic. This leads to cache poisoning. This allows any client, including browser scripts, to bypass local security and poison the browser cache and any downstream caches with content from an arbitrary source. Squid uses a string search instead of parsing the Transfer-Encoding header to find chunked encoding. This allows an attacker to hide a second request inside Transfer-Encoding: it is interpreted by Squid as chunked and split out into a second request delivered upstream. Squid will then deliver two distinct responses to the client, corrupting any downstream caches. |
2 |
CVE-2020-11709 |
74 |
|
Http R.Spl. |
2020-04-12 |
2020-04-13 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
cpp-httplib through 0.5.8 does not filter \r\n in parameters passed into the set_redirect and set_header functions, which creates possibilities for CRLF injection and HTTP response splitting in some specific contexts. |
3 |
CVE-2020-11703 |
74 |
|
Http R.Spl. |
2020-04-12 |
2020-04-13 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
An issue was discovered in ProVide (formerly zFTPServer) through 13.1. /ajax/GetInheritedProperties allows HTTP Response Splitting via the language parameter. |
4 |
CVE-2020-7695 |
74 |
|
Http R.Spl. |
2020-07-27 |
2023-01-31 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
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. |
5 |
CVE-2020-7622 |
|
|
Http R.Spl. |
2020-04-06 |
2021-08-03 |
7.5 |
None |
Remote |
Low |
Not required |
Partial |
Partial |
Partial |
This affects the package io.jooby:jooby-netty before 1.6.9, from 2.0.0 and before 2.2.1. The DefaultHttpHeaders is set to false which means it does not validates that the header isn't being abused for HTTP Response Splitting. |
6 |
CVE-2020-6858 |
74 |
|
Http R.Spl. |
2020-03-12 |
2020-03-17 |
4.3 |
None |
Remote |
Medium |
Not required |
None |
Partial |
None |
Hotels Styx through 1.0.0.beta8 allows HTTP response splitting due to CRLF Injection. This is exploitable if untrusted user input can appear in a response header. |
7 |
CVE-2020-6181 |
|
|
Http R.Spl. |
2020-02-12 |
2020-02-21 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
Under some circumstances the SAML SSO implementation in the SAP NetWeaver (SAP_BASIS versions 702, 730, 731, 740 and SAP ABAP Platform (SAP_BASIS versions 750, 751, 752, 753, 754), allows an attacker to include invalidated data in the HTTP response header sent to a Web user, leading to HTTP Response Splitting vulnerability. |
8 |
CVE-2020-5249 |
74 |
|
XSS Http R.Spl. |
2020-03-02 |
2020-04-09 |
4.0 |
None |
Remote |
Low |
??? |
None |
Partial |
None |
In Puma (RubyGem) before 4.3.3 and 3.12.4, if an application using Puma allows untrusted input in an early-hints header, an attacker can use a carriage return character to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to CVE-2020-5247, which fixed this vulnerability but only for regular responses. This has been fixed in 4.3.3 and 3.12.4. |
9 |
CVE-2020-5247 |
113 |
|
XSS Http R.Spl. |
2020-02-28 |
2022-10-12 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
In Puma (RubyGem) before 4.3.2 and before 3.12.3, if an application using Puma allows untrusted input in a response header, an attacker can use newline characters (i.e. `CR`, `LF` or`/r`, `/n`) to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as HTTP Response Splitting. While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to CVE-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server. This has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters. |
10 |
CVE-2019-19670 |
|
|
XSS Http R.Spl. |
2020-02-10 |
2020-02-11 |
4.3 |
None |
Remote |
Medium |
Not required |
None |
Partial |
None |
A HTTP Response Splitting vulnerability was identified in the Web Settings Component of Web File Manager in Rumpus FTP Server 8.2.9.1. A successful exploit can result in stored XSS, website defacement, etc. via ExtraHTTPHeader to RAPR/WebSettingsGeneralSet.html. |
11 |
CVE-2019-16385 |
79 |
|
XSS Http R.Spl. |
2020-06-04 |
2021-07-21 |
4.3 |
None |
Remote |
Medium |
Not required |
None |
Partial |
None |
Cybele Thinfinity VirtualUI 2.5.17.2 allows HTTP response splitting via the mimetype parameter within a PDF viewer request, as demonstrated by an example.pdf?mimetype= substring. The victim user must load an application request to view a PDF, containing the malicious payload. This results in a reflected XSS payload being executed. |
12 |
CVE-2019-10797 |
|
|
Http R.Spl. |
2020-02-19 |
2020-03-02 |
4.3 |
None |
Remote |
Medium |
Not required |
None |
Partial |
None |
Netty in WSO2 transport-http before v6.3.1 is vulnerable to HTTP Response Splitting due to HTTP Header validation being disabled. |
13 |
CVE-2019-4552 |
|
|
XSS Http R.Spl. +Info |
2020-10-15 |
2020-10-20 |
5.8 |
None |
Remote |
Medium |
Not required |
Partial |
Partial |
None |
IBM Security Access Manager 9.0.7 and IBM Security Verify Access 10.0.0 are vulnerable to HTTP response splitting attacks. A remote attacker could exploit this vulnerability using specially-crafted URL to cause the server to return a split response, once the URL is clicked. This would allow the attacker to perform further attacks, such as Web cache poisoning, cross-site scripting, and possibly obtain sensitive information. IBM X-Force ID: 165960. |
14 |
CVE-2015-3154 |
74 |
|
Http R.Spl. |
2020-01-27 |
2020-01-30 |
4.3 |
None |
Remote |
Medium |
Not required |
None |
Partial |
None |
CRLF injection vulnerability in Zend\Mail (Zend_Mail) in Zend Framework before 1.12.12, 2.x before 2.3.8, and 2.4.x before 2.4.1 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in the header of an email. |