Response content control via proxy login header injection
Published Feb 16, 2023 · Updated Oct 22, 2024
HTTP response splitting in Fortinet FortiOS and FortiProxy allows remote authenticated users to control response headers and body content. The proxy login page incorporates attacker-controlled CRLF sequences into HTTP response headers without neutralization, splitting the response. A valid authenticated session and network access to the proxy login interface are required; impact is limited to response content control.
Summary
What happened
HTTP response splitting in Fortinet FortiOS and FortiProxy allows remote authenticated users to control response headers and body content. The proxy login page incorporates attacker-controlled CRLF sequences into HTTP response headers without neutralization, splitting the response. A valid authenticated session and network access to the proxy login interface are required; impact is limited to response content control.
The record
- CVE
- CVE-2022-42472
- Published
- Feb 16, 2023
- Updated
- Oct 22, 2024
- Vendor
- Fortinet
- Product
- FortiOS
- Classifications
- CWE-113, CWE-436
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 16, 2023CVE publishedPublication date reported by the CVE source.
- Oct 22, 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=6.0.0 <=6.0.16
- Affected versionversion=6.2.0 <=6.2.12
- Affected versionversion=6.4.0 <=6.4.11
- Affected versionversion=7.0.0 <=7.0.8
- Affected versionversion=7.2.0 <=7.2.2
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