agoo prior to 2.14.0 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable. HTTP pipelining issues and request smuggling attacks might be possible due to incorrect Content-Length and Transfer encoding header parsing. It is possible to conduct HTTP request smuggling attacks where `agoo` is used as part of a chain of backend servers due to insufficient `Content-Length` and `Transfer Encoding` parsing.
CVE Status: Modified
Attribute | Value |
---|---|
Attack Complexity | LOW |
Attack Vector | NETWORK |
Availability Impact | NONE |
Base Score | 7.5 |
Base Severity | HIGH |
Confidentiality Impact | NONE |
Integrity Impact | HIGH |
Privileges Required | NONE |
Scope | UNCHANGED |
User Interaction | NONE |
Vector String | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Exploitability Score | 3.9 |
Impact Score | 3.6 |
Source | [email protected] |
Type | Primary |