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.
References
Configurations
History
21 Nov 2024, 05:37
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130 - | |
References | () https://github.com/ohler55/agoo/issues/88 - | |
References | () https://snyk.io/vuln/SNYK-RUBY-AGOO-569137 - Third Party Advisory |
Information
Published : 2020-06-10 16:15
Updated : 2024-11-21 05:37
NVD link : CVE-2020-7670
Mitre link : CVE-2020-7670
CVE.ORG link : CVE-2020-7670
JSON object : View
Products Affected
ohler
- agoo
CWE
CWE-444
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')