Quick answers
- Is CVE-2016-5682 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2016-5682 being exploited in the wild.
- How severe is CVE-2016-5682?
- Informational severity, with a CVSS score of 0, published 1 September 2020.
- Which products and versions are affected?
- swagger-ui (npm) SEMVER:introduced=0,fixed=2.2.1.
- Is there a fix for CVE-2016-5682?
- Yes. swagger-ui (npm): upgrade to 2.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2016-5682 attacked?
- It is attacked over the network.
- Am I affected by CVE-2016-5682?
- Check whether you run swagger-ui (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- swagger-ui (npm): upgrade to 2.2.1 or later
npm install swagger-ui@2.2.1
Technical details
This is a cross-site scripting (CWE-79) vulnerability in swagger-ui's rendering of JSON schema definitions. The vulnerable code fails to properly escape property names when displaying them in the UI, allowing JavaScript code embedded in property keys (e.g., "<script>alert(1)</script>") to execute in the browser. The attack is client-side: an attacker provides a URL to a malicious JSON schema file via the url query string parameter, which swagger-ui loads and renders without sanitizing the property names. No authentication is required—any user can be tricked into accessing a swagger-ui instance with a malicious URL. The impact is full XSS in the user's browser context. The vulnerability was fixed in version 2.2.1 and later.
Affected products
- SmartBear Software swagger-ui before 2.2.1
Identifiers
- CVE-2016-5682
- GHSA-p239-93f7-h6xf
Timeline
- 2016-01-13: disclosed: Issue reported on GitHub
- 2016: patched: Fixed in version 2.2.1
- 2020-09-01: advisory: Advisory GHSA-p239-93f7-h6xf published