Cross-Site Scripting in swagger-ui

published 2020-09-11 6y ago modified 2021-09-28 5y ago

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

Versions of `swagger-ui` prior to 3.20.9 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize URLs used in the OAuth auth flow, which may allow attackers to execute arbitrary JavaScript.

## Recommendation

Upgrade to version 3.20.9 or later.

Patch / fix

fixed in 1 links 2

npm swagger-ui 3.20.9

github.com/swagger-api/swagger-ui@1e184e8 commit
github.com/swagger-api/swagger-ui#5190 pull request

Is GHSA-4f9m-pxwh-68hg 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

CVSS scores

assigned by	version	score	vector
GitHub	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	swagger-ui	<3.20.9	3.20.9

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

GitHub Advisory GHSA-4f9m-pxwh-68hg

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.