Request smuggling via retained vulnerable Netty parser
Published Apr 11, 2022 · Updated Aug 2, 2024
HTTP request smuggling in Red Hat OpenShift Logging 3.11 allows remote attackers to poison proxied HTTP/1.1 requests. The Elasticsearch 6 container retains a vulnerable Netty HTTP codec that fails to validate Content-Length when one HTTP/2 headers frame ends the stream before translation. Exploitation requires a proxy path that translates attacker-controlled HTTP/2 requests to HTTP/1.1, allowing request-boundary confusion and downstream request injection.
Summary
What happened
HTTP request smuggling in Red Hat OpenShift Logging 3.11 allows remote attackers to poison proxied HTTP/1.1 requests. The Elasticsearch 6 container retains a vulnerable Netty HTTP codec that fails to validate Content-Length when one HTTP/2 headers frame ends the stream before translation. Exploitation requires a proxy path that translates attacker-controlled HTTP/2 requests to HTTP/1.1, allowing request-boundary confusion and downstream request injection.
The record
- CVE
- CVE-2022-0552
- Published
- Apr 11, 2022
- Updated
- Aug 2, 2024
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift Logging
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=origin-aggregated-logging versions 3.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo