Response splitting via disabled Netty header validation
Published Apr 6, 2020 · Updated Sep 16, 2024
HTTP response splitting in Jooby Netty before 1.6.9 and 2.0.0 through 2.2.0 allows remote attackers to inject response data. NettyContext constructs DefaultHttpHeaders with validation disabled, so carriage-return and line-feed characters in attacker-controlled header data are accepted. Exploitation requires an application to place attacker-controlled data in a response header and enables cross-site scripting, cache poisoning, or page hijacking.
Summary
What happened
HTTP response splitting in Jooby Netty before 1.6.9 and 2.0.0 through 2.2.0 allows remote attackers to inject response data. NettyContext constructs DefaultHttpHeaders with validation disabled, so carriage-return and line-feed characters in attacker-controlled header data are accepted. Exploitation requires an application to place attacker-controlled data in a response header and enables cross-site scripting, cache poisoning, or page hijacking.
The record
- CVE
- CVE-2020-7622
- Published
- Apr 6, 2020
- Updated
- Sep 16, 2024
- Vendor
- Jooby Project
- Product
- Jooby Netty
- Classifications
- CWE-113, CAPEC-34, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 6, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=2.0.0 <unspecified
- Affected versionversion=unspecified <1.6.9
- Affected versionversion=unspecified <2.2.1
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