GHSA-82mf-mmh7-hxp5 json
Directory traversal in development mode handler in Vaadin 14 and 15-17
published 5y ago modified last yr.
- cvss
- 5.9
- 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
Improper URL validation in development mode handler in `com.vaadin:flow-server` versions 2.0.0 through 2.4.1 (Vaadin 14.0.0 through 14.4.2), and 3.0 prior to 5.0 (Vaadin 15 prior to 18) allows attacker to request arbitrary files stored outside of intended frontend resources folder.
- https://vaadin.com/security/cve-2020-36321
Patch / fix
- maven com.vaadin:vaadin-bom 14.4.3, 18.0.0
Is GHSA-82mf-mmh7-hxp5 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 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | com.vaadin:vaadin-bom | >=14.0.0, <14.4.3 >=15.0.0, <18.0.0 |
14.4.3 18.0.0 |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
Sources
- GitHub Advisory GHSA-82mf-mmh7-hxp5
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.