Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

GHSA-vh5w-fg69-rc8m

MEDIUMFix: google/closure-library@294fc00

GHSA-vh5w-fg69-rc8m is a medium-severity (CVSS 6.5) CWE-625 vulnerability in google-closure-library. O3 Security confirms whether GHSA-vh5w-fg69-rc8m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Input Validation in Google Closure Library

Also known asCVE-2020-8910
Published
May 7, 2021
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

55other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
google-closure-librarynpm
41Kdownloads / week

Description

A URL parsing issue in goog.uri of the Google Closure Library versions up to and including v20200224 allows an attacker to send malicious URLs to be parsed by the library and return the wrong authority. Mitigation -- update your library to version v20200315.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmgoogle-closure-libraryall versions20200315.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google-closure-library. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update google-closure-library to 20200315.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vh5w-fg69-rc8m is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-vh5w-fg69-rc8m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vh5w-fg69-rc8m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A URL parsing issue in goog.uri of the Google Closure Library versions up to and including v20200224 allows an attacker to send malicious URLs to be parsed by the library and return the wrong authority. Mitigation -- update your library to version v20200315.
O3 Security · Impact-Aware SCA

Is GHSA-vh5w-fg69-rc8m in your dependencies?

O3 detects GHSA-vh5w-fg69-rc8m across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-vh5w-fg69-rc8m: Improper Input… | O3 Security