Echo: BodyDump can discard BodyLimit overflow errors for unknown-length requests
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Echo Go web framework, specifically its version 5 BodyDump middleware, is affected. Requests with unknown body length (such as chunked HTTP/1.1 requests) can be silently truncated when they exceed the configured body size limit, and the truncated request may then be processed as if it were complete.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Echo is a Go web framework. From 5.0.0 until 5.4.1, Echo v5's BodyDump middleware can discard a BodyLimit overflow error for an unknown-length request when BodyDump's capture limit is below the BodyLimit threshold. BodyDump drains the remaining body while ignoring read errors and replaces it with the captured prefix, so an HTTP/1.1 chunked request can be truncated and processed successfully even though the original body exceeded the configured limit. Known-length requests rejected before BodyDump runs are unaffected, and the issue does not establish a general authentication bypass or denial of service. This issue is fixed in 5.4.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- labstack echo
From 5.0.0 · fixed in 5.4.1
- github.com/labstack/echo/v5Go
From 5.0.0 · fixed in 5.4.1