Skip to content

GHSA-c6c4-7x48-4cqp

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

Medium Maven
Severity
4.0 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-208 Observable Timing Discrepancy
Fix
10.0.17
Upgrade com.vaadin:vaadin-bom to this version or later

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 prior to 14), 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.

Affected versions

Maven

PackageVulnerableFixed in
com.vaadin:vaadin-bom
>= 10.0.0, < 10.0.17
10.0.17
com.vaadin:vaadin-bom
>= 11.0.0, < 14.4.7
14.4.7
com.vaadin:vaadin-bom
>= 15.0.0, < 18.0.6
18.0.6

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

com.vaadin:vaadin-bom Maven → 10.0.17

maven
<dependency><groupId>com.vaadin</groupId><artifactId>vaadin-bom</artifactId><version>10.0.17</version></dependency>
gradle
implementation("com.vaadin:vaadin-bom:10.0.17")

Severity breakdown

CVSS 3.1 4.0

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

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

Weakness

CWE-208: Observable Timing Discrepancy

Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-93c4-vf86-3rj7
Reflected cross-site scripting in vaadin-menu-bar webjar resources in Vaadin 14
Medium Also affects com.vaadin:vaadin-bom
GHSA-jfmf-w293-8xr8
Regular expression Denial of Service (ReDoS) in EmailValidator class in V7 compatibility module in Vaadin 8
High Also affects com.vaadin:vaadin-bom
GHSA-hw7r-qrhp-5pff
Unauthorized property update in CheckboxGroup component in Vaadin 12-14 and 15-20
Medium Also affects com.vaadin:vaadin-bom
GHSA-c99r-67x4-whj6
Reflected cross-site scripting in development mode handler in Vaadin 14, 15-19
Low Also affects com.vaadin:vaadin-bom
GHSA-qrg9-f472-qwfm
Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19
Medium Also affects com.vaadin:vaadin-bom
GHSA-p826-8vhq-h439
Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19
Medium Also affects com.vaadin:vaadin-bom
GHSA-mr8h-j9cv-4m8h
Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19
Medium Also affects com.vaadin:vaadin-bom
GHSA-75xc-qvxh-27f8
Timing side channel vulnerability in UIDL request handler in Vaadin 7 and 8
Medium Also affects com.vaadin:vaadin-bom
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor