CVE-2025-29914: Github.com/jptosso/coraza waf OWASP Coraza WAF Has Parser Vulnerability

MODERATE
Advisory Identifier: GHSA-q9f5-625g-xm39
CVSS 5.4
CWE-706
Published
Advisory Summary

CVE-2025-29914 is a MODERATE (CVSS 5.4) owasp coraza waf has parser vulnerability (CWE-706: Use of Incorrectly-Resolved Name or Reference) affecting Github.com/jptosso/coraza waf libraries in the Go ecosystem. The issue involves owasp coraza waf has parser confusion which leads to wrong uri in `request_filename`. Remediation is available by upgrading affected packages to version 3.3.3.

CVE-2025-29914 at a Glance

CVE Identifier CVE-2025-29914
GHSA Identifier GHSA-q9f5-625g-xm39
Severity MODERATE
CVSS v3.1 Base Score 5.4
CWE Classification CWE-706: Use of Incorrectly-Resolved Name or Reference
Affected Product Github.com/jptosso/coraza waf
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2025-29914

To remediate this vulnerability, upgrade all affected Github.com/jptosso/coraza waf dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/jptosso/coraza-waf fixed: 3.3.3
Upgrade github.com/jptosso/coraza-waf to 3.3.3
github.com/corazawaf/coraza/v3 fixed: 3.3.3
Upgrade github.com/corazawaf/coraza/v3 to 3.3.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/jptosso/coraza-waf

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-29914, inspect your project dependencies for Github.com/jptosso/coraza waf:

inspect dependencies for github.com/jptosso/coraza-waf

Analyze the terminal output to locate any version of Github.com/jptosso/coraza waf in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.3.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-706: Use of Incorrectly-Resolved Name or Reference, where the product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. In Github.com/jptosso/coraza waf, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary URLs starting with `//` are not parsed properly, and the request `REQUEST_FILENAME` variable contains a wrong value, leading to potential rules bypass. ### Details If a request is made on an URI starting with `//`, coraza will set a wrong value in `REQUEST_FILENAME`. For example, if the URI `//bar/uploads/foo.php?a=b` is passed to coraza: , `REQUEST_FILENAME` will be set to `/uploads/foo.php`. The root cause is the usage of `url.Parse` to parse the URI in [ProcessURI](https://github.com/corazawaf/coraza/blob/8b612f4e6e18c606e371110227bc7669dc714cab/internal/corazawaf/transaction.go#L768). `url.Parse` can parse both absolute URLs (starting with a scheme) or relative ones (just the path). `//bar/uploads/foo.php` is a valid absolute URI (the scheme is empty), `url.Parse` will consider `bar` as the host and the path will be set to `/uploads/foo.php`. ### PoC ```go package main import ( "fmt" "net/url" "os" "github.com/corazawaf/coraza/v3" ) const testRule = ` SecDebugLogLevel 9 SecDebugLog /dev/stdout SecRule REQUEST_FILENAME "@rx /bar/uploads/.*\.(h?ph(p|tm?l?|ar)|module|shtml)" "id:1,phase:1,deny" ` func main() { var testURL = "//bar/uploads/foo.php" if os.Getenv("TEST_URL") != "" { testURL = os.Getenv("TEST_URL") } fmt.Printf("Testing URL: %s\n", testURL) config := coraza.NewWAFConfig().WithDirectives(testRule) waf, err := coraza.NewWAF(config) if err != nil { panic(err) } tx := waf.NewTransaction() tx.ProcessURI(testURL, "GET", "HTTP/1.1") in := tx.ProcessRequestHeaders() if in != nil { fmt.Printf("%+v\n", in) } } ``` ### Impact Potential bypass of rules using `REQUEST_FILENAME`.

CVE-2025-29914 Affected Github.com/jptosso/coraza waf Versions

2 component(s)
Fixed Versions:
3.3.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/jptosso/coraza-waf
Go
< 3.3.3
3.3.3
github.com/corazawaf/coraza/v3
Go
< 3.3.3
3.3.3

References

Frequently Asked Questions

What is CVE-2025-29914?
CVE-2025-29914 is a security vulnerability in Github.com/jptosso/coraza waf involving OWASP Coraza WAF has parser confusion which leads to wrong URI in `REQUEST_FILENAME` under CWE-706: Use of Incorrectly-Resolved Name or Reference.
Which Github.com/jptosso/coraza waf versions are affected?
Affected versions include releases prior to 3.3.3 across affected packages: github.com/jptosso/coraza-waf, github.com/corazawaf/coraza/v3.
What version fixes CVE-2025-29914?
Upgrading to 3.3.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/jptosso/coraza-waf affected?
Yes, github.com/jptosso/coraza-waf is affected in releases prior to 3.3.3. Upgrade your dependency to 3.3.3 or later.
Is github.com/corazawaf/coraza/v3 affected?
Yes, github.com/corazawaf/coraza/v3 is affected in releases prior to 3.3.3. Upgrade your dependency to 3.3.3 or later.
What is the CVSS score of CVE-2025-29914?
CVE-2025-29914 has a CVSS v3.1 base score of 5.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2025-29914?
CVE-2025-29914 is classified under CWE-706: Use of Incorrectly-Resolved Name or Reference (The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.).
How can I check Go dependencies for CVE-2025-29914?
Run the dependency tree command: 'inspect dependencies for github.com/jptosso/coraza-waf'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q9f5-625g-xm39",
  "modified" : "2025-03-20T18:48:38Z",
  "published" : "2025-03-20T18:48:38Z",
  "aliases" : [ "CVE-2025-29914" ],
  "summary" : "OWASP Coraza WAF has parser confusion which leads to wrong URI in `REQUEST_FILENAME`",
  "details" : "### Summary\n\nURLs starting with `//` are not parsed properly, and the request `REQUEST_FILENAME` variable contains a wrong value, leading to potential rules bypass.\n\n### Details\n\nIf a request is made on an URI starting with `//`, coraza will set a wrong value in `REQUEST_FILENAME`.\nFor example, if the URI `//bar/uploads/foo.php?a=b` is passed to coraza: , `REQUEST_FILENAME` will be set to `/uploads/foo.php`.\n\nThe root cause is the usage of `url.Parse` to parse the URI in [ProcessURI](https://github.com/corazawaf/coraza/blob/8b612f4e6e18c606e371110227bc7669dc714cab/internal/corazawaf/transaction.go#L768).\n\n`url.Parse` can parse both absolute URLs (starting with a scheme) or relative ones (just the path). \n`//bar/uploads/foo.php` is a valid absolute URI (the scheme is empty), `url.Parse` will consider `bar` as the host and the path will be set to `/uploads/foo.php`.\n\n### PoC\n\n```go\npackage main\n\nimport (\n\t\"fmt\"\n\t\"net/url\"\n\t\"os\"\n\n\t\"github.com/corazawaf/coraza/v3\"\n)\n\nconst testRule = `\nSecDebugLogLevel 9\nSecDebugLog /dev/stdout\nSecRule REQUEST_FILENAME \"@rx /bar/uploads/.*\\.(h?ph(p|tm?l?|ar)|module|shtml)\" \"id:1,phase:1,deny\"\n`\n\nfunc main() {\n\tvar testURL = \"//bar/uploads/foo.php\"\n\n\tif os.Getenv(\"TEST_URL\") != \"\" {\n\t\ttestURL = os.Getenv(\"TEST_URL\")\n\t}\n\n\tfmt.Printf(\"Testing URL: %s\\n\", testURL)\n\n\tconfig := coraza.NewWAFConfig().WithDirectives(testRule)\n\n\twaf, err := coraza.NewWAF(config)\n\n\tif err != nil {\n\t\tpanic(err)\n\t}\n\n\ttx := waf.NewTransaction()\n\n\ttx.ProcessURI(testURL, \"GET\", \"HTTP/1.1\")\n\n\tin := tx.ProcessRequestHeaders()\n\n\tif in != nil {\n\t\tfmt.Printf(\"%+v\\n\", in)\n\t}\n}\n```\n\n### Impact\n\nPotential bypass of rules using `REQUEST_FILENAME`.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/jptosso/coraza-waf"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.3.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/corazawaf/coraza/v3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.3.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/corazawaf/coraza/security/advisories/GHSA-q9f5-625g-xm39"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-29914"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/corazawaf/coraza/commit/4722c9ad0d502abd56b8d6733c6b47eb4111742d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/corazawaf/coraza"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-706" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-03-20T18:48:38Z",
    "nvd_published_at" : "2025-03-20T18:15:18Z"
  }
}