How to fix: Vulnerable Dependency (OSV-Confirmed)
A client-side library loaded by this page, at the exact version detected from its script filename, has a published vulnerability in OSV.dev (the Open Source Vulnerabilities database, which aggregates GitHub Security Advisories, npm audit advisories, and other ecosystem-specific sources). See the finding evidence for which library, version, and advisory.
Why it matters
Depends on the specific advisory; see the finding evidence for the exact CVE/GHSA identifier and its own impact description.
The library name and version are read from the script's own filename or CDN URL (e.g. jquery-1.12.4.min.js, or a version-pinned CDN path like unpkg.com/[email protected]/...), the same passive, safe-by-construction technique lib/scanner/checks/page-checks/libraries.ts uses. Unlike that check's small, hand-maintained table of known-vulnerable ranges, this one queries OSV.dev live, so it reflects whatever OSV currently knows about the exact detected version rather than a fixed set of CVEs picked at one point in time.
How to fix it
- 1Upgrade the library past the vulnerable range named in the finding evidence.
- 2If the library is bundled rather than loaded from a CDN, update it in the project's dependency manifest (package.json/package-lock.json) and rebuild.
- 3Re-run this scan after the fix to confirm OSV.dev no longer returns a match for the new version.
Code examples
Pin the fixed version instead of the vulnerable one
<!-- Bad: pinned to the version OSV.dev flagged in the finding evidence -->
<script src="https://code.jquery.com/jquery-1.8.2.min.js"></script>
<!-- Good: pinned to a version at or after the advisory's fixed range -->
<script src="https://code.jquery.com/jquery-3.7.1.min.js"></script>References
Detected automatically by VulnRadar. The check id is osv-vulnerable-library, stable across every scan so you can filter or diff on it.
More supply chain checks
- Mediumnpm/yarn Lock File Exposed
- MediumPython Requirements File Exposed
- MediumRuby Gemfile or Gemfile.lock Exposed
- MediumExternal CDN Script Without SRI Hash
- HighHTTP Script Loaded on HTTPS Page
- MediumPHP composer.json or composer.lock Exposed
- HighDockerfile or docker-compose.yml Exposed
- Critical.env File Exposed at Public URL
Questions
- How severe is Vulnerable Dependency (OSV-Confirmed)?
- VulnRadar rates this high severity in the supply chain category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id osv-vulnerable-library, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Vulnerable Dependency (OSV-Confirmed) map to?
- It maps to CWE-1104.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.