Cross-Site Scripting in google-closure-library

published 2020-09-02 6y ago modified 2021-09-27 5y ago

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 1

npm google-closure-library 20190301.0.0

github.com/google/closure-library@c79ab48 commit

Is GHSA-r9q4-w3fm-wrm2 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	google-closure-library	<20190301.0.0	20190301.0.0

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

GitHub Advisory GHSA-r9q4-w3fm-wrm2

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.