dbcve.org
Jboss FuseApplication · Redhat

CVE-2016-1000229

MEDIUM · 6.1 CVSS v3.1 Published 2019-12-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
swagger-ui has XSS in key names

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-site scripting (XSS) vulnerability in swagger-ui allows injection of malicious JavaScript through API key names that are not properly sanitized or encoded before being rendered in the web interface.

MitigationApply proper output encoding/sanitization to all key names displayed in the swagger-ui, and implement Content Security Policy headers to mitigate XSS risks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jboss FuseApplication
Affected:= 6.3
OpenshiftApplication
Affected:= 2.0
Swagger UiApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if swagger-ui is deployed in your environment
    Search for swagger-ui files, check application manifests, or scan for swagger-ui endpoints (typically at /swagger-ui, /swagger, /api-docs, or /swagger-ui/index.html) in your web server logs or configuration
    Affected if swagger-ui is found and accessible in your environment
  2. Determine the swagger-ui version
    Check the swagger-ui JavaScript file (swagger-ui-bundle.js or older versions like swagger-ui.js) for version comments, or check package.json/dependencies if using a packaged version. Compare against affected versions: Smartbear all versions, Redhat Jboss Fuse 6.3, Redhat Openshift 2.0
    Affected if The installed version matches any affected product version listed in the CVE
  3. Check if API key authentication is configured in your swagger spec
    Open your swagger.json or OpenAPI specification file and examine the securityDefinitions (OpenAPI 2.0) or security schemes (OpenAPI 3.0) section. Look for security schemes with type: apiKey
    Affected if API key authentication is defined in your swagger specification
  4. Inspect how swagger-ui renders API key name fields
    View the swagger-ui HTML page source or the swagger-ui bundle JavaScript. Look for the code that renders the apiKey input field (typically in the auth plugin or apidefinition plugin). Check if the key name from your swagger spec is inserted into the DOM without encoding
    Affected if The API key name from your swagger spec is displayed in the UI without proper HTML encoding
  5. Verify Content Security Policy headers are absent or weak
    Check HTTP response headers from your swagger-ui endpoint for Content-Security-Policy header. If absent or does not include 'unsafe-inline' restrictions, XSS execution is possible
    Affected if CSP headers are missing or allow inline scripts (unsafe-inline)

Your environment is affected if swagger-ui is deployed, uses an affected version, and has API key authentication configured in the swagger spec with key names rendered in the web interface without encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply proper output encoding/sanitization to all key names displayed in the swagger-ui, and implement Content Security Policy headers to mitigate XSS risks.

Fix this in Jboss Fuse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1000229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1000229 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data