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.
References
Link | Resource |
---|---|
https://github.com/postrank-labs/goliath/issues/351%2C | |
https://snyk.io/vuln/SNYK-RUBY-GOLIATH-569136 | Third Party Advisory |
https://github.com/postrank-labs/goliath/issues/351%2C | |
https://snyk.io/vuln/SNYK-RUBY-GOLIATH-569136 | Third Party Advisory |
Configurations
History
21 Nov 2024, 05:37
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/postrank-labs/goliath/issues/351%2C - | |
References | () https://snyk.io/vuln/SNYK-RUBY-GOLIATH-569136 - Third Party Advisory |
07 Nov 2023, 03:26
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2020-06-10 16:15
Updated : 2024-11-21 05:37
NVD link : CVE-2020-7671
Mitre link : CVE-2020-7671
CVE.ORG link : CVE-2020-7671
JSON object : View
Products Affected
goliath_project
- goliath
CWE
CWE-444
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')