CVE-2020-7670
agoo prior to 2.14.0 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.17%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.1
- 7.5 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- EPSS
- 1.17% probability · 66th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-444
- Affected
- ohler/agoo
- Source
- report@snyk.io
References
- https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130
- https://github.com/ohler55/agoo/issues/88
- https://snyk.io/vuln/SNYK-RUBY-AGOO-569137Third Party Advisory
- https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130
- https://github.com/ohler55/agoo/issues/88
- https://snyk.io/vuln/SNYK-RUBY-AGOO-569137Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.