How severe is GHSA-r9q4-w3fm-wrm2?

No CVSS score has been assigned to GHSA-r9q4-w3fm-wrm2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r9q4-w3fm-wrm2?

GHSA-r9q4-w3fm-wrm2 affects the following packages: google-closure-library (npm). Ecosystems affected: npm.

How do I fix GHSA-r9q4-w3fm-wrm2?

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

How do I detect GHSA-r9q4-w3fm-wrm2 in my npm dependencies?

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.

How do I mitigate GHSA-r9q4-w3fm-wrm2 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-r9q4-w3fm-wrm2?

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

Is GHSA-r9q4-w3fm-wrm2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-r9q4-w3fm-wrm2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-r9q4-w3fm-wrm2 published, and has it been updated?

GHSA-r9q4-w3fm-wrm2 was published on September 2, 2020 and was last updated on September 27, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-r9q4-w3fm-wrm2

Fix: google/closure-library@c79ab48

GHSA-r9q4-w3fm-wrm2 is a security vulnerability in google-closure-library. O3 Security confirms whether GHSA-r9q4-w3fm-wrm2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in google-closure-library

Published

Sep 2, 2020

Updated

Sep 27, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 2021 · OSV.dev, 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

39Kdownloads / week

Description

Versions of google-closure-library prior to 20190301.0.0 are vulnerable to Cross-Site Scripting. The safedomtreeprocessor.processToString() function improperly processed empty elements, which could allow attackers to execute arbitrary JavaScript through Mutation Cross-Site Scripting.

Recommendation

Upgrade to version 20190301.0.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`google-closure-library`	all versions	20190301.0.0

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update google-closure-library to 20190301.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9q4-w3fm-wrm2 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-r9q4-w3fm-wrm2 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-r9q4-w3fm-wrm2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `google-closure-library` prior to 20190301.0.0 are vulnerable to Cross-Site Scripting. The `safedomtreeprocessor.processToString()` function improperly processed empty elements, which could allow attackers to execute arbitrary JavaScript through Mutation Cross-Site Scripting. ## Recommendation Upgrade to version 20190301.0.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-r9q4-w3fm-wrm2 in your dependencies?

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

Scan my dependencies How O3 SCA works