WAF rule bypass via network-path URI confusion
Published Mar 20, 2025 · Updated Mar 20, 2025
Improper URI parsing in Coraza before 3.3.3 allows remote attackers to bypass REQUEST_FILENAME-based rules with double-slash paths. ProcessURI passes a network-path reference to url.Parse, which treats the first path segment as a host and stores only the remaining path in REQUEST_FILENAME. Exploitation requires a rule that relies on REQUEST_FILENAME; matching requests can evade that rule and reach protected application resources.
Summary
What happened
Improper URI parsing in Coraza before 3.3.3 allows remote attackers to bypass REQUEST_FILENAME-based rules with double-slash paths. ProcessURI passes a network-path reference to url.Parse, which treats the first path segment as a host and stores only the remaining path in REQUEST_FILENAME. Exploitation requires a rule that relies on REQUEST_FILENAME; matching requests can evade that rule and reach protected application resources.
The record
- CVE
- CVE-2025-29914
- Published
- Mar 20, 2025
- Updated
- Mar 20, 2025
- Vendor
- Coraza WAF
- Product
- Coraza
- Classifications
- CWE-20, CWE-706, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 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.3.3
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
- Upstream ProcessURI proof of conceptproof of concept · demonstrated
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