
Cloud Vulnerability DB
A community-led vulnerabilities database
In a Yarn classic (v1) project, a dependency declared through an npm alias, for example "util-lib": "npm:lodash@4.17.20", is looked up under the wrong package name. Yarn 1.22 writes the lockfile key util-lib@npm:lodash@4.17.20 and installs lodash@4.17.20, but the Yarn classic parser takes everything before the last @ as the name, so the scan queries OSV for util-lib@npm:lodash, finds nothing, and reports "No known vulnerabilities found".
The scan exits 0 even under --fail-on high, so a CI gate relying on the scanner passes over a known vulnerable package. The same lodash@4.17.20 declared directly reports 4 CVEs, including CVE-2021-23337, and exits 1.
Confirmed on v1.41.0 and on main at 77bde74.
Treat @npm: as the alias marker in the Yarn classic parser and the Yarn lock graph, keep the install name, and resolve the registry package (scoped targets and the no-range form included). After the fix the same project reports the 4 CVEs, suggests yarn add util-lib@npm:lodash@4.18.1, and exits 1.
Reported by @alex-powell.
Source: NVD
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."