GHSA-pxg6-pf52-xh8x

cookie accepts cookie name, path, and domain with out of bounds characters

Low highest severity reported · also known as CVE-2024-47764

2
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.7%
EPSS for CVE-2024-47764, percentile 55

Catalog tools matching GHSA-pxg6-pf52-xh8x

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1cookie@0.4.0
npm
0.7.0not analyzedember-electron/backend/package-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1cookie@0.4.2
npm
0.7.0not analyzedpackage-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1cookie@0.5.0
npm
0.7.0not analyzedpackage-lock.jsonDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3cookie@0.4.0
npm
0.7.0not analyzedpackage-lock.jsonDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3cookie@0.4.2
npm
0.7.0not analyzedts-binary-wrapper/package-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-pxg6-pf52-xh8x · NVD CVE-2024-47764 · OSV GHSA-pxg6-pf52-xh8x

Grype data sources: https://github.com/advisories/GHSA-pxg6-pf52-xh8x