Skip to content
Fencer Intel
medium 4.0

GHSA-c6c4-7x48-4cqp json

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

published 5y ago modified last yr.

cvss
4.0
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

- https://vaadin.com/security/cve-2021-31404

Patch / fix

  • maven com.vaadin:vaadin-bom 10.0.17, 14.4.7, 18.0.6

Is GHSA-c6c4-7x48-4cqp in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 4.0 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven com.vaadin:vaadin-bom
>=10.0.0, <10.0.17
>=11.0.0, <14.4.7
>=15.0.0, <18.0.6
10.0.17
14.4.7
18.0.6

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.