Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in org.webjars.npm:undici

Summary

undici's retry interceptor can append the body of a ranged retry response to bytes already delivered from an earlier partial response while still presenting the original response's status and headers. This happens when an upstream server delivers part of a body without a trustworthy resume checkpoint, for example a non-success response whose headers were already sent or a partial-content response with an unusable content range, then closes the connection and answers the resumed range request with more bytes. As a result the response body can be longer than the Content-Length that the application observes. An application that relays such a response to a downstream HTTP/1.1 peer without normalizing the framing can emit a body that exceeds the forwarded Content-Length, and the excess bytes can be interpreted as the start of a following response, which enables downstream response splitting or desynchronization. Exploitation requires an attacker-controlled upstream server and an application that forwards the response through a framing-sensitive path. This affects undici versions prior to 6.28.1, from 7.x prior to 7.29.1, and from 8.0.0 prior to 8.10.2. Users should upgrade to undici 6.28.1, 7.29.1, or 8.10.2.