Security readout for executives and security teams
Plain-English summary
A Vaadin development-mode component could let a remote attacker read files outside the intended frontend resources directory. The issue is confidentiality-focused: the published CVSS vector shows high confidentiality impact, with no integrity or availability impact. Exposure depends on using affected Vaadin or flow-server versions with the vulnerable development-mode handler reachable.
Executive priority
Treat as a moderate-priority exposure check. Prioritize internet-facing Vaadin applications and environments where development mode may be enabled. The main business risk is unauthorized file disclosure, potentially including configuration or secrets if reachable through traversal.
Technical view
CVE-2020-36321 is a CWE-22 directory traversal caused by improper URL validation in Vaadin Flow's development mode handler. Affected ranges include com.vaadin:flow-server 2.0.0 through 2.4.1, Vaadin 14.0.0 through 14.4.2, and flow-server 3.0 prior to 5.0, corresponding to Vaadin 15 prior to 18.
Likely exposure
Most relevant exposure is Java applications using affected Vaadin Flow versions, especially where development mode or its handler is accessible over a network. Production systems not running affected versions or not exposing development-mode behavior are less likely to be exposed.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The CVSS vector is network-accessible, unauthenticated, and no user interaction, but with high attack complexity and read-only confidentiality impact.
Researcher notes
Evidence supports directory traversal in the development-mode handler and affected version ranges. The bundle does not provide exploit telemetry, proof-of-concept detail, or comprehensive fixed-version instructions beyond non-affected version boundaries. Avoid assuming broader Vaadin products or active exploitation without additional vendor or KEV evidence.
Mitigation direction
- Upgrade Vaadin or flow-server outside the affected ranges cited by Vaadin.
- Ensure development mode is disabled on production deployments.
- Restrict network access to any development-only endpoints or tooling.
- Review Vaadin's advisory for supported upgrade guidance.
- Audit deployments for unexpected frontend resource handler exposure.
Validation and detection
- Inventory Vaadin and com.vaadin:flow-server versions in application dependencies.
- Confirm production deployments are not running Vaadin development mode.
- Review routing and reverse-proxy rules exposing Vaadin development handlers.
- Check logs for unusual requests targeting frontend resource paths.
- Verify dependency updates with unit and regression tests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-36321 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://vaadin.com/security/cve-2020-36321CVE reference · x_refsource_MISC
- https://github.com/vaadin/flow/pull/9392CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.