GHSA-p6mc-m468-83gw

Prototype Pollution in lodash

High highest severity reported · also known as CVE-2020-8203

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
5.2%
EPSS for CVE-2020-8203, percentile 93

Catalog tools matching GHSA-p6mc-m468-83gw

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
sysdig-inspect
Container Security › Runtime Security
0.12.1lodash.pick@4.4.0
npm
no fix listednot analyzedpackage-lock.jsonDispute
eslint-plugin-security
Static Application Security Testing (SAST) › Language-specific › JavaScript/Node.js
eslint-plugin-security-v4.2.1lodash@4.17.5
npm
4.17.19not analyzedpackage-lock.jsonDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3lodash.pick@4.4.0
npm
no fix listednot analyzedpackage-lock.jsonDispute
snyk-cli
Software Composition Analysis (SCA)
v1.1308.3lodash.set@4.3.2
npm
no fix listednot 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-p6mc-m468-83gw · NVD CVE-2020-8203 · OSV GHSA-p6mc-m468-83gw

Grype data sources: https://github.com/advisories/GHSA-p6mc-m468-83gw