WAF filter bypass via malformed HTTP requests
Published Nov 2, 2022 · Updated Oct 25, 2024
Improper request handling in Fortinet FortiADC 5.0.0 through 6.2.3 and 7.0.0 through 7.0.2 allows remote attackers to bypass WAF filters. The WAF request-processing path accepts malformed HTTP syntax without consistently applying its SQL injection and cross-site scripting filters; Fortinet has not published the responsible parser or validation routine. No authentication or user interaction is required, but the direct impact is limited to evasion of configured WAF protections rather than compromise of FortiADC itself.
Summary
What happened
Improper request handling in Fortinet FortiADC 5.0.0 through 6.2.3 and 7.0.0 through 7.0.2 allows remote attackers to bypass WAF filters. The WAF request-processing path accepts malformed HTTP syntax without consistently applying its SQL injection and cross-site scripting filters; Fortinet has not published the responsible parser or validation routine. No authentication or user interaction is required, but the direct impact is limited to evasion of configured WAF protections rather than compromise of FortiADC itself.
The record
- CVE
- CVE-2022-38381
- Published
- Nov 2, 2022
- Updated
- Oct 25, 2024
- Vendor
- Fortinet
- Product
- FortiADC
- Classifications
- CWE-228
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 2, 2022CVE publishedPublication date reported by the CVE source.
- Oct 25, 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=FortiADC 7.0.2, 7.0.1, 7.0.0, 6.2.3, 6.2.2, 6.2.1, 6.2.0, 6.1.6, 6.1.5, 6.1.4, 6.1.3, 6.1.2, 6.1.1, 6.1.0, 6.0.4, 6.0.3, 6.0.2, 6.0.1, 6.0.0, 5.4.5, 5.4.4, 5.4.3, 5.4.2, 5.4.1, 5.4.0, 5.3.7, 5.3.6, 5.3.5, 5.3.4, 5.3.3, 5.3.2, 5.3.1, 5.3.0, 5.2.8, 5.2.7, 5.2.6, 5.2.5, 5.2.4, 5.2.3, 5.2.2, 5.2.1, 5.2.0, 5.1.7, 5.1.6, 5.1.5, 5.1.4, 5.1.3, 5.1.2, 5.1.1, 5.1.0, 5.0.4, 5.0.3, 5.0.2, 5.0.1, 5.0.0
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