CyberRota Analysis
AI-GeneratedThe vulnerability affects applications utilizing undici's retry interceptor, which can improperly handle responses from upstream servers, leading to a mismatch between the actual body length and the Content-Length header. This can result in invalid HTTP responses, causing downstream response desynchronization, connection hangs, or response corruption. Organizations using undici versions prior to 6.28.0, 7.29.0, or 8.9.0, particularly those operating proxies or gateways that forward headers and bodies, should prioritize patching to mitigate potential exploitation risks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
undici's retry interceptor can deliver a response whose body length does not match the Content-Length header exposed to the application after a retry or resume of a partial response. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, a malicious or faulty upstream can return a partial response with a mismatched framing header, close the socket early, and have the retry interceptor assemble a body of a different length while the original Content-Length stays attached. Applications that use the retry interceptor and forward upstream headers and bodies downstream, such as proxies or gateways, may then emit an invalid HTTP response with a stale Content-Length, leading to downstream response desynchronization, connection hangs, or response corruption. Exploitation requires the retry interceptor enabled, an upstream returning a mismatched partial response, and a downstream forwarder that does not remove or recalculate Content-Length. The issue is fixed in undici 6.28.0, 7.29.0, and 8.9.0.
Related CVEs
Other vulnerabilities affecting the same vendor(s)