GHSA-9wv6-86v2-598j

path-to-regexp outputs backtracking regular expressions

High highest severity reported · also known as CVE-2024-45296

3
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog
0.9%
EPSS for CVE-2024-45296, percentile 61

Catalog tools matching GHSA-9wv6-86v2-598j

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1path-to-regexp@0.1.7
npm
0.1.10not analyzedpackage-lock.jsonDispute
gatekeeper
Policy as Code
v3.23.1path-to-regexp@1.8.0
npm
1.9.0not analyzedwebsite/yarn.lockDispute
gatekeeper
Policy as Code
v3.23.1path-to-regexp@2.2.1
npm
3.3.0not analyzedwebsite/yarn.lockDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3path-to-regexp@0.1.7
npm
0.1.10not analyzedpackage-lock.jsonDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3path-to-regexp@1.8.0
npm
1.9.0not analyzedpackage-lock.jsonDispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-9wv6-86v2-598j · NVD CVE-2024-45296 · OSV GHSA-9wv6-86v2-598j

Grype data sources: https://github.com/advisories/GHSA-9wv6-86v2-598j