goliath through 1.0.6 allows request smuggling attacks where goliath is used as a backend and a frontend proxy also being vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks.
Advisories
Source ID Title
EUVD EUVD EUVD-2021-0916 goliath through 1.0.6 allows request smuggling attacks where goliath is used as a backend and a frontend proxy also being vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks.
Github GHSA Github GHSA GHSA-3892-2r52-p65m HTTP Request Smuggling in goliath
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:01.215Z

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

Link: CVE-2020-7671

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

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

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

Link: CVE-2020-7671

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses