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.
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Flow | Vaadin | 1.0.0 (including) | 1.0.14 (including) |
| Flow | Vaadin | 1.1.0 (including) | 1.4.0 (including) |
| Flow | Vaadin | 2.0.0 (including) | 2.6.1 (including) |
| Flow | Vaadin | 3.0.0 (including) | 5.0.0 (including) |
| Flow | Vaadin | 6.0.0 (including) | 6.0.9 (including) |
| Vaadin | Vaadin | 10.0.0 (including) | 10.0.18 (including) |
| Vaadin | Vaadin | 11.0.0 (including) | 13.0.0 (including) |
| Vaadin | Vaadin | 14.0.0 (including) | 14.6.1 (including) |
| Vaadin | Vaadin | 15.0.0 (including) | 18.0.0 (including) |
| Vaadin | Vaadin | 19.0.0 (including) | 19.0.8 (including) |
Debug messages are messages that help troubleshoot an issue by revealing the internal state of the system. For example, debug data in design can be exposed through internal memory array dumps or boot logs through interfaces like UART via TAP commands, scan chain, etc. Thus, the more information contained in a debug message, the easier it is to debug. However, there is also the risk of revealing information that could help an attacker either decipher a vulnerability, and/or gain a better understanding of the system. Thus, this extra information could lower the “security by obscurity” factor. While “security by obscurity” alone is insufficient, it can help as a part of “Defense-in-depth”.