GHSA-vh95-rmgr-6w4m

Prototype Pollution in minimist

Medium highest severity reported · also known as CVE-2020-7598

1
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
1.9%
EPSS for CVE-2020-7598, percentile 80

Catalog tools matching GHSA-vh95-rmgr-6w4m

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1minimist@0.0.10
npm
0.2.1not analyzedember-electron/backend/package-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1minimist@0.0.8
npm
0.2.1not analyzedlib/wsd-core/package-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1minimist@1.1.3
npm
1.2.3not analyzedpackage-lock.jsonDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1minimist@1.2.0
npm
1.2.3not analyzedember-electron/backend/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-vh95-rmgr-6w4m · NVD CVE-2020-7598 · OSV GHSA-vh95-rmgr-6w4m

Grype data sources: https://github.com/advisories/GHSA-vh95-rmgr-6w4m