GHSA-6hgr-2g6q-3rmc json
Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19
published 5y ago modified last yr.
- cvss
- 6.3
- 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
`Authentication.logout()` helper in `com.vaadin:flow-client` versions 5.0.0 prior to 6.0.0 (Vaadin 18), and 6.0.0 through 6.0.4 (Vaadin 19.0.0 through 19.0.3) uses incorrect HTTP method, which, in combination with Spring Security CSRF protection, allows local attackers to access Fusion endpoints after the user attempted to log out.
- https://vaadin.com/security/cve-2021-31408
Patch / fix
- maven com.vaadin:flow-client 6.0.5
- github.com/vaadin/flow@815b967 commit
- github.com/vaadin/flow#10577 pull request
Is GHSA-6hgr-2g6q-3rmc 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 | 6.3 | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.vaadin:flow-client | >=5.0.0, <6.0.5 |
6.0.5 |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
Sources
- GitHub Advisory GHSA-6hgr-2g6q-3rmc
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.