Affected versions of actix-http do not track quoted strings when parsing
HTTP/1.1 chunk extensions. A carriage return inside a quoted extension value
is treated as the end of the chunk-size line, even if the closing quote is
missing. For example, 0;x="\r\n\r\n is accepted as the end of a chunked body,
and a following pipelined request is dispatched on the same connection.
A remote client can trigger this without authentication. CR and LF are invalid inside HTTP quoted strings, including after a backslash; they must be rejected rather than interpreted as framing or accepted as quoted data.
Request smuggling requires an upstream intermediary that forwards the malformed input while using a different request boundary. Dispatching two requests on the sender's own connection does not by itself demonstrate an authorization bypass or an effect on another user. Proxy bypass, cache poisoning, and cross-user response mixing were not demonstrated by the reproduction.
Upgrade to actix-http 3.21.3 or later. The fix preserves quote and escape state
across reads and rejects invalid control bytes inside quoted strings and quoted
pairs before consuming the following body or request bytes.
{
"license": "CC-BY-4.0"
}