Header injection via unneutralized CRLF sequences
Published Jan 3, 2023 · Updated Oct 22, 2024
HTTP response splitting in the FortiWeb API allows remote authenticated users to inject arbitrary HTTP response headers. Fortinet identifies improper CRLF neutralization in the API but has not published the affected endpoint, field, or underlying implementation error. The attack requires valid API access and user interaction; the published impact is limited to header injection, with no reported code execution or service interruption.
Summary
What happened
HTTP response splitting in the FortiWeb API allows remote authenticated users to inject arbitrary HTTP response headers. Fortinet identifies improper CRLF neutralization in the API but has not published the affected endpoint, field, or underlying implementation error. The attack requires valid API access and user interaction; the published impact is limited to header injection, with no reported code execution or service interruption.
The record
- CVE
- CVE-2022-42471
- Published
- Jan 3, 2023
- Updated
- Oct 22, 2024
- Vendor
- Fortinet
- Product
- FortiWeb
- Classifications
- CWE-113, CWE-74
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 3, 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.3.6 <=6.3.21
- Affected versionversion=6.4.0 <=6.4.2
- Affected versionversion=7.0.0 <=7.0.2
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