GHSA-hrpp-h998-j3pp

qs vulnerable to Prototype Pollution

High highest severity reported · also known as CVE-2022-24999

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
15.7%
EPSS for CVE-2022-24999, percentile 97

Catalog tools matching GHSA-hrpp-h998-j3pp

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1qs@6.4.0
npm
6.4.1not analyzedpackage-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1qs@6.5.2
npm
6.5.3not analyzedpackage-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1qs@6.7.0
npm
6.7.3not analyzedember-electron/backend/package-lock.jsonDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3qs@6.7.0
npm
6.7.3not 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-hrpp-h998-j3pp · NVD CVE-2022-24999 · OSV GHSA-hrpp-h998-j3pp

Grype data sources: https://github.com/advisories/GHSA-hrpp-h998-j3pp