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.0.13 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize YAML files imported from URLs or copied-pasted. This may allow attackers to execute arbitrary JavaScript.

## Recommendation

Upgrade to version 3.0.13 or later.

Patch / fix

fixed in 1

npm swagger-ui 3.0.13

Is GHSA-388g-jwpg-x6j4 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:R/S:U/C:H/I:N/A:N

Affected packages

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

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

github.com /swagger-api/swagger-ui/issues/3163
web
github.com /swagger-api/swagger-ui
package
snyk.io /vuln/SNYK-JS-SWAGGERUI-449941
web
npmjs.com /advisories/985
web

Sources

GitHub Advisory GHSA-388g-jwpg-x6j4

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.