Loading vulnerability…
CVE-2016-1000229 is a cross-site scripting vulnerability in swagger-ui caused by improper neutralization of untrusted input rendered from key names. An attacker can supply crafted key names that are interpreted as active script content by the user interface, resulting in execution of attacker-controlled script in the victim's browser within the application context. Reported affected deployments include container releases prior to CF196 in products embedding the vulnerable component; on-premise deployments are stated to be unaffected in that product context.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains two pairs of files (YAML and JSON) that serve as exploit payloads for CVE-2016-1000229, a cross-site scripting (XSS) vulnerability in Swagger UI. The main exploit files are 'exploit.yaml' and 'exploit2.yaml', which are crafted Swagger/OpenAPI definitions embedding XSS payloads in the 'info' section (title and description fields). The payloads include HTML and SVG elements with embedded JavaScript (e.g., <img onerror=alert(document.domain) src=1>), designed to trigger JavaScript execution when the definition is loaded in a vulnerable Swagger UI instance. The JSON files ('exploit.json' and 'exploit2.json') reference the corresponding YAML files and provide metadata. The repository does not contain executable code but provides proof-of-concept payloads for manual or automated testing of Swagger UI instances. The main attack vector is via the browser, targeting users who load the malicious API definitions. The basePath '/test/' is specified in both YAML files, which may be relevant for fingerprinting affected endpoints.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.