CVE-2020-36319: Potential sensitive data exposure in applications using Vaadin 15

CVE-2020-36319 · Severity: low · CVSS 3.1 · Published 2021-04-19

Potential sensitive data exposure in applications using Vaadin 15

Technologies: com.vaadin:flow-server (Maven). Vendors: Maven.

Quick answers

Is CVE-2020-36319 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-36319 being exploited in the wild.
How severe is CVE-2020-36319?
Low severity, with a CVSS score of 3.1, published 19 April 2021.
Which products and versions are affected?
com.vaadin:flow-server (Maven) ECOSYSTEM:introduced=3.0.0,fixed=3.0.6.
Is there a fix for CVE-2020-36319?
Yes. com.vaadin:flow-server (Maven): upgrade to 3.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-36319?
Check whether you run com.vaadin:flow-server (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • com.vaadin:flow-server (Maven): upgrade to 3.0.6 or later
    # set com.vaadin:flow-server to 3.0.6 in your pom.xml or build.gradle

Affected products

  • com.vaadin:flow-server (Maven) ECOSYSTEM:introduced=3.0.0,fixed=3.0.6

Identifiers

  • CVE-2020-36319
  • GHSA-rjww-2x8v-m9v9

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.