HTTP response splitting via unsanitized Netty headers
Published Sep 19, 2023 · Updated Feb 13, 2025
HTTP response splitting in Apache Flink Stateful Functions 3.1.0 through 3.2.0 allows remote attackers to inject headers via crafted HTTP requests. NettyRequestReplyHandler constructed HTTP headers without rejecting CR/LF characters, allowing attacker-controlled input to create additional header lines. Exploitation requires a crafted request to reach that path; the resulting response can carry phishing content or script.
Summary
What happened
HTTP response splitting in Apache Flink Stateful Functions 3.1.0 through 3.2.0 allows remote attackers to inject headers via crafted HTTP requests. NettyRequestReplyHandler constructed HTTP headers without rejecting CR/LF characters, allowing attacker-controlled input to create additional header lines. Exploitation requires a crafted request to reach that path; the resulting response can carry phishing content or script.
The record
- CVE
- CVE-2023-41834
- Published
- Sep 19, 2023
- Updated
- Feb 13, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Flink Stateful Functions
- Classifications
- CWE-113, CWE-74, T1056.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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=3.1.0 <=3.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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