Loading vulnerability…
CVE-2019-17495 is a CSS injection vulnerability in Swagger UI before version 3.23.11. The issue arises from Swagger UI’s handling of untrusted remotely supplied JSON/OpenAPI content, which can be embedded and rendered in a way that permits attacker-controlled style directives. By leveraging Relative Path Overwrite (RPO), an attacker can inject CSS through malicious JSON content, including the use of style import directives, and cause the browser to apply attacker-influenced styles within the Swagger UI context. This enables CSS-based exfiltration of values present in rendered input fields, including sensitive anti-forgery tokens.
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.
Single-file repository containing a malicious Swagger/OpenAPI 2.0 JSON document used as a proof of concept for CVE-2019-17495 affecting Swagger UI. The file, cve-2019-17495-poc.json, embeds multiple javascript: URLs into standard metadata fields such as termsOfService, contact.url, license.url, tag descriptions, operation descriptions, parameter descriptions, response descriptions, and externalDocs.url. Its purpose is to show that vulnerable Swagger UI versions render these fields unsafely, allowing XSS when a user clicks links or opens them in a new tab. The PoC specifically targets https://nwopen-api.nwo.nl/NWOpen-API and also documents a reflected XSS vector at /api/Projects using the role query parameter with payload <img src=x onerror=alert(1)>. This is a browser/web attack, not a standalone exploit framework module, and it provides demonstration payloads rather than post-exploitation capability.
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.
4 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.