Summary
Netty's HTTP/1.1 handling incorrectly parses quoted strings in chunked transfer encoding extension values in affected versions.
When front-end and back-end components disagree on how to interpret these extensions, an attacker can perform HTTP request smuggling, potentially bypassing security controls and confusing downstream services.
Affected context
This vulnerability appears in applications and services that:
- Use Netty as the HTTP/1.1 server or client framework
- Accept or forward HTTP requests using chunked transfer encoding
- Sit behind or in front of other HTTP-aware components (e.g., reverse proxies, load balancers, API gateways, WAFs)
The issue is triggered when Netty's parsing of chunked transfer encoding extension values, especially with quoted strings, diverges from how other HTTP components in the chain parse the same data.
Exploit preconditions
- Attack surface: HTTP/1.1 endpoints that accept chunked transfer encoding requests through Netty.
- Required access: Ability to send crafted HTTP requests to an affected Netty-based service (typically unauthenticated network access to the HTTP interface).
- Trigger point: Parsing of
Transfer-Encoding: chunkedrequests that include carefully constructed chunk extensions with quoted strings. - Why exploitation is possible: Netty's parsing logic for chunked encoding extensions differs from that of other HTTP components in the request path, allowing an attacker to desynchronize their view of where one request ends and the next begins.
Why this happens
The root cause is an inconsistency in Netty's HTTP/1.1 chunked transfer encoding parser when handling quoted strings in chunk extension values.
According to HTTP specifications, intermediaries and servers must agree on how to interpret chunked messages, including any extension parameters.
Netty's parser treats certain quoted extension sequences differently than upstream or downstream components, leading to message boundary confusion.
This maps to CWE-444: Inconsistent Interpretation of HTTP Requests, where different implementations interpret the same HTTP stream in incompatible ways, enabling attackers to inject or smuggle additional requests through desynchronization rather than through syntactic violations alone.
Potential impact
- Bypass of HTTP security controls such as WAFs, rate limiters, or authentication gateways.
- Smuggling of hidden requests to backend services that the front-end proxy did not intend to forward.
- Execution of actions as a different user context if smuggled requests are processed within an authenticated connection.
- Cache poisoning or cache desynchronization on shared HTTP caches.
- Abuse of internal-only endpoints that are expected to be unreachable from the public internet.
General mitigation guidance
Defensive strategies focus on enforcing consistent and conservative HTTP parsing across the request chain and minimizing trust in complex encodings:
- Align HTTP parsing behavior between edge components (e.g., load balancers, reverse proxies) and Netty by adhering to strict, spec-compliant parsing rules for transfer encoding and extensions.
- Normalize or strip non-essential chunked transfer encoding extensions at a trusted boundary, reducing ambiguity in how extensions are interpreted.
- Prefer simpler and explicit request framing (e.g.,
Content-Lengthfor known-size requests) where operationally viable, reducing exposure to chunked parsing edge cases. - Apply least-privilege design to backend endpoints so that even if a smuggled request reaches them, accessible functionality and data are tightly constrained.
- Configure front-end infrastructure to reject or sanitize suspicious or malformed chunked requests, especially those with unusual extension syntax or quoting patterns.
How teams detect issues like this
Detection typically combines configuration review, code analysis, and runtime monitoring:
- Use static analysis or code review to identify custom HTTP parsing, relaxed validation logic, or direct reliance on nuanced chunked extension semantics within Netty-based services.
- Review reverse proxy and load balancer configurations to ensure consistent HTTP/1.1 parsing behavior and to identify permissive settings for chunked transfer encoding and extensions.
- Employ security testing tools or dynamic scanners designed to probe for HTTP request smuggling by sending crafted chunked requests and analyzing backend behavior.
- Monitor logs for anomalies such as mismatched request counts between front-end and back-end, unexpected 400/408/502 errors, or unexplained requests appearing on backend logs without corresponding entries at the edge.
- Integrate automated HTTP hardening checks into CI/CD and deployment pipelines to flag risky parser configurations or non-standard behaviors.

