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.
Advisories
Source ID Title
EUVD EUVD EUVD-2020-1430 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.
Github GHSA Github GHSA GHSA-h385-52j6-9984 Withdrawn: HTTP Request Smuggling in Agoo
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: snyk

Published:

Updated: 2024-08-04T09:41:00.497Z

Reserved: 2020-01-21T00:00:00

Link: CVE-2020-7670

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2020-06-10T16:15:10.540

Modified: 2024-11-21T05:37:34.810

Link: CVE-2020-7670

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses