GHSA-c57f-4vp2-jqhm json
Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-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
Insecure temporary directory usage in frontend build functionality of `com.vaadin:flow-server` versions 2.0.9 through 2.5.2 (Vaadin 14.0.3 through Vaadin 14.5.2), 3.0 prior to 6.0 (Vaadin 15 prior to 19), and 6.0.0 through 6.0.5 (Vaadin 19.0.0 through 19.0.4) allows local users to inject malicious code into frontend resources during application rebuilds.
- https://vaadin.com/security/cve-2021-31411
Patch / fix
- maven com.vaadin:flow-server 2.5.3, 6.0.6
Is GHSA-c57f-4vp2-jqhm 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:L/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.vaadin:flow-server | >=2.0.9, <2.5.3 >=3.0.0, <6.0.6 |
2.5.3 6.0.6 |
Classification
- Weakness
-
- CWE-379 Creation of Temporary File in Directory with Insecure Permissions
References
Sources
- GitHub Advisory GHSA-c57f-4vp2-jqhm
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.