Skip to content

GHSA-p826-8vhq-h439 CVE-2021-31411

Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-19

Medium Maven
Severity
6.3 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.23%
Chance of exploitation in the next 30 days. Higher than 14.06% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-379 Creation of Temporary File in Directory with Insecure Permissions
Fix
14.5.3
Upgrade com.vaadin:vaadin-bom to this version or later

Description

Insecure temporary directory usage in frontend build functionality of com.vaadin:flow-server versions 2.0.9 through 2.5.2 (Vaadin 14.0.3 through Vaadin 14.5.2), 3.0 prior to 6.0 (Vaadin 15 prior to 19), and 6.0.0 through 6.0.5 (Vaadin 19.0.0 through 19.0.4) allows local users to inject malicious code into frontend resources during application rebuilds.

Affected versions

Maven

PackageVulnerableFixed in
com.vaadin:vaadin-bom
>= 14.0.3, < 14.5.3
14.5.3
com.vaadin:vaadin-bom
>= 15.0.0, < 19.0.5
19.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 → 14.5.3

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

Severity breakdown

CVSS 3.1 6.3

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

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

Weakness

CWE-379: Creation of Temporary File in Directory with Insecure Permissions

The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.

How to prevent it
  • Requirements: Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.
  • Implementation: Try to store sensitive tempfiles in a directory which is not world readable -- i.e., per-user directories.
  • Implementation: Avoid using vulnerable temp file functions.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
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-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
GHSA-q74r-4xw3-ppx9
Stored cross-site scripting in Grid component 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