Skip to content

Timing side channel vulnerability in UIDL request handler in Vaadin 10, 11-14, and 15-18

Moderate severity GitHub Reviewed Published Apr 16, 2021 in vaadin/flow • Updated Feb 1, 2023

Package

maven com.vaadin:flow-server (Maven)

Affected versions

>= 1.0.0, < 1.0.14
>= 1.1.0, < 2.4.7
>= 3.0.0, < 5.0.3

Patched versions

1.0.14
2.4.7
5.0.3

Description

Non-constant-time comparison of CSRF tokens in UIDL request handler in com.vaadin:flow-server versions 1.0.0 through 1.0.13 (Vaadin 10.0.0 through 10.0.16), 1.1.0 prior to 2.0.0 (Vaadin 11 through 13), 2.0.0 through 2.4.6 (Vaadin 14.0.0 through 14.4.6), 3.0.0 prior to 5.0.0 (Vaadin 15 prior to 18), and 5.0.0 through 5.0.2 (Vaadin 18.0.0 through 18.0.5) allows attacker to guess a security token via timing attack.

References

@fluorumlabs fluorumlabs published to vaadin/flow Apr 16, 2021
Reviewed Apr 16, 2021
Published to the GitHub Advisory Database Apr 19, 2021
Published by the National Vulnerability Database Apr 23, 2021
Last updated Feb 1, 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
Local
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
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:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.044%
(14th percentile)

Weaknesses

CVE ID

CVE-2021-31404

GHSA ID

GHSA-xwg3-qrcg-w9x6

Source code

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