Skip to content

Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19

Moderate severity GitHub Reviewed Published Jun 24, 2021 in vaadin/platform • Updated Jan 29, 2023

Package

maven com.vaadin:vaadin-bom (Maven)

Affected versions

>= 10.0.0, <= 10.0.18
>= 11.0.0, < 14.0.0
>= 15.0.0, <= 19.0.8

Patched versions

10.0.19
14.6.2
19.0.9

Description

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.

References

@fluorumlabs fluorumlabs published to vaadin/platform Jun 24, 2021
Published by the National Vulnerability Database Jun 24, 2021
Reviewed Jun 24, 2021
Published to the GitHub Advisory Database Jun 28, 2021
Last updated Jan 29, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.085%
(38th percentile)

Weaknesses

CVE ID

CVE-2021-31412

GHSA ID

GHSA-qrg9-f472-qwfm

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.