CVE-2020-36321 json
Directory traversal in development mode handler in Vaadin 14 and 15-17
published 5y ago modified 4mo ago also GHSA-49r2-73m6-pp8f , EUVD-2021-0753
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- 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.
Patch / fix
- maven com.vaadin:flow-server 2.4.2, 5.0.0
- Vaadin Vaadin 18.0.0
- Vaadin flow-server 5.0.0
- github.com/vaadin/flow#9392 pull request
Is CVE-2020-36321 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 FencerExploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| 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:flow-server | >=3.0.0, <5.0.0 >=2.0.0, <2.4.2 |
5.0.0 2.4.2 |
Affected products
- Vaadin Vaadin
- Vaadin flow-server
Classification
References
-
github.com
/vaadin/flow/pull/9392
web, patch, third-party-advisory
-
vaadin.com
/security/cve-2020-36321
web, vendor-advisory
-
github.com
/vaadin/flow/security/advisories/GHSA-49r2-73m6-pp8f
web
-
nvd.nist.gov
/vuln/detail/CVE-2020-36321
advisory
Sources
- CVE List CVE-2020-36321
- GitHub Advisory GHSA-49r2-73m6-pp8f
- NVD CVE-2020-36321
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.