Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2020-11077 | First vendor Publication | 2020-05-22 |
Vendor | Cve | Last vendor Modification | 2023-11-07 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | |||
---|---|---|---|
Overall CVSS Score | 7.5 | ||
Base Score | 7.5 | Environmental Score | 7.5 |
impact SubScore | 3.6 | Temporal Score | 7.5 |
Exploitabality Sub Score | 3.9 | ||
Attack Vector | Network | Attack Complexity | Low |
Privileges Required | None | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | None |
Integrity Impact | High | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : (AV:N/AC:L/Au:N/C:N/I:P/A:N) | |||
---|---|---|---|
Cvss Base Score | 5 | Attack Range | Network |
Cvss Impact Score | 2.9 | Attack Complexity | Low |
Cvss Expoit Score | 10 | Authentication | None Required |
Calculate full CVSS 2.0 Vectors scores |
Detail
In Puma (RubyGem) before 4.3.5 and 3.12.6, a client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client. If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client. This is a similar but different vulnerability from CVE-2020-11076. The problem has been fixed in Puma 3.12.6 and Puma 4.3.5. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11077 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-444 | Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') |
CPE : Common Platform Enumeration
Type | Description | Count |
---|---|---|
Application | 1 | |
Os | 1 | |
Os | 1 | |
Os | 2 |
Sources (Detail)
Alert History
Date | Informations |
---|---|
2023-11-07 21:37:16 |
|
2023-03-03 17:27:44 |
|
2021-05-04 13:44:57 |
|
2021-04-22 02:56:51 |
|
2020-10-07 17:22:49 |
|
2020-09-26 05:22:45 |
|
2020-07-19 09:22:46 |
|
2020-07-19 00:22:45 |
|
2020-05-28 21:23:07 |
|
2020-05-23 02:41:34 |
|