Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 14.0.0, 2.0.0, 10.0.19, 14.6.2, 19.0.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Improper sanitization of path in default RouteNotFoundError view in com.vaadin:flow-server versions 1.0.0 through 1.0.14 (Vaadin 10.0.0 through 10.0.18), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), and 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows network attacker to enumerate all available routes via crafted HTTP request when application is running in production mode and no custom handler for NotFoundException is provided.
Timeline
- CVE published
- Record last updated
Affected versions
- Vaadin Vaadin
From 10.0.0; through 10.0.18; From 11.0.0; fixed in 14.0.0; From 14.0.0; through 14.6.1; From 15.0.0; through 19.0.8
- Vaadin flow-server
From 1.0.0; through 1.0.14; From 1.1.0; fixed in 2.0.0; From 2.0.0; through 2.6.1; From 3.0.0; through 6.0.9
- com.vaadin:vaadin-bomMaven
From 10.0.0 · fixed in 10.0.19
- com.vaadin:vaadin-bomMaven
From 11.0.0 · fixed in 14.6.2
- com.vaadin:vaadin-bomMaven
From 15.0.0 · fixed in 19.0.9