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.

AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

CWE-444

https://cna.openjsf.org/security-advisories.html

https://github.com/nodejs/undici/security/advisories/GHSA-8xcm-r25x-g524

[{"vendor":"undici","product":"undici","defaultStatus":"unaffected","packageURL":"pkg:npm/undici","versions":[{"version":"0","lessThan":"6.28.0","versionType":"semver","status":"affected"},{"version":"6.28.0","versionType":"semver","status":"unaffected"},{"version":"7.0.0","lessThan":"7.29.0","versionType":"semver","status":"affected"},{"version":"7.29.0","versionType":"semver","status":"unaffected"},{"version":"8.0.0","lessThan":"8.9.0","versionType":"semver","status":"affected"},{"version":"8.9.0","versionType":"semver","status":"unaffected"}]}]