GHSA-9h6g-6mxg-vvp4 json
Timing side channel vulnerability in endpoint request handler in Vaadin 15-19
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 endpoint request handler in `com.vaadin:flow-server` versions 3.0.0 through 5.0.3 (Vaadin 15.0.0 through 18.0.6), and com.vaadin:fusion-endpoint version 6.0.0 (Vaadin 19.0.0) allows attacker to guess a security token for Fusion endpoints via timing attack.
- https://vaadin.com/security/cve-2021-31406
Patch / fix
- maven com.vaadin:vaadin-bom 18.0.7, 19.0.1
Is GHSA-9h6g-6mxg-vvp4 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 FencerCVSS 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 | >=19.0.0, <19.0.1 >=15.0.0, <18.0.7 |
19.0.1 18.0.7 |
Classification
- Weakness
-
- CWE-208 Observable Timing Discrepancy
References
Sources
- GitHub Advisory GHSA-9h6g-6mxg-vvp4
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.