Skip to content

GHSA-76f4-fw33-6j2v

Potential sensitive data exposure in applications using Vaadin 15

Low Maven
Severity
3.1 / 10
Low · CVSS 3.1
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
15.0.5
Upgrade com.vaadin:vaadin-bom to this version or later

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

Affected versions

Maven

PackageVulnerableFixed in
com.vaadin:vaadin-bom
>= 15.0.0, < 15.0.5
15.0.5

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

com.vaadin:vaadin-bom Maven → 15.0.5

maven
<dependency><groupId>com.vaadin</groupId><artifactId>vaadin-bom</artifactId><version>15.0.5</version></dependency>
gradle
implementation("com.vaadin:vaadin-bom:15.0.5")

Severity breakdown

CVSS 3.1 3.1

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-93c4-vf86-3rj7
Reflected cross-site scripting in vaadin-menu-bar webjar resources in Vaadin 14
Medium Also affects com.vaadin:vaadin-bom
GHSA-jfmf-w293-8xr8
Regular expression Denial of Service (ReDoS) in EmailValidator class in V7 compatibility module in Vaadin 8
High Also affects com.vaadin:vaadin-bom
GHSA-hw7r-qrhp-5pff
Unauthorized property update in CheckboxGroup component in Vaadin 12-14 and 15-20
Medium Also affects com.vaadin:vaadin-bom
GHSA-c99r-67x4-whj6
Reflected cross-site scripting in development mode handler in Vaadin 14, 15-19
Low Also affects com.vaadin:vaadin-bom
GHSA-qrg9-f472-qwfm
Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19
Medium Also affects com.vaadin:vaadin-bom
GHSA-p826-8vhq-h439
Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19
Medium Also affects com.vaadin:vaadin-bom
GHSA-mr8h-j9cv-4m8h
Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19
Medium Also affects com.vaadin:vaadin-bom
GHSA-75xc-qvxh-27f8
Timing side channel vulnerability in UIDL request handler in Vaadin 7 and 8
Medium Also affects com.vaadin:vaadin-bom
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor