CVE-2019-17495
CRITICALCVE-2019-17495 is a critical-severity (CVSS 9.8) Cross-Site Request Forgery (CSRF) vulnerability in org.webjars:swagger-ui. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2019-17495 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Cross-site scripting in Swagger-UI
Blast Radius
org.webjars:swagger-ui☕org.webjars.npm:swagger-ui☕io.springfox:springfox-swagger-ui📦swagger-uiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A Cascading Style Sheets (CSS) injection vulnerability in Swagger UI before 3.23.11 allows attackers to use the Relative Path Overwrite (RPO) technique to perform CSS-based input field value exfiltration, such as exfiltration of a CSRF token value. In other words, this product intentionally allows the embedding of untrusted JSON data from remote servers, but it was not previously known that <style>@import within the JSON data was a functional attack method.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.webjars:swagger-ui | all versions | 3.23.11 |
| ☕Maven | org.webjars.npm:swagger-ui | all versions | 3.23.11 |
| ☕Maven | io.springfox:springfox-swagger-ui | all versions | 2.10.0 |
| 📦npm | swagger-ui | all versions | 3.23.11 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.webjars:swagger-ui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.webjars:swagger-ui to 3.23.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-17495 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2019-17495 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2019-17495. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-17495 in your dependencies?
O3 detects CVE-2019-17495 across Maven, npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.