Skip to content

Duplicate Advisory: Insecure Temporary File in RESTEasy

Moderate severity GitHub Reviewed Published Feb 18, 2023 to the GitHub Advisory Database • Updated Jan 15, 2025
Withdrawn This advisory was withdrawn on Jan 15, 2025

Package

maven org.jboss.resteasy:resteasy-core (Maven)

Affected versions

< 4.7.8.Final
>= 5.0.0.Alpha1, < 5.0.6.Final
>= 6.0.0.Beta1, < 6.2.3.Final

Patched versions

4.7.8.Final
5.0.6.Final
6.2.3.Final
maven org.jboss.resteasy:resteasy-multipart-provider (Maven)
< 4.7.8.Final
>= 5.0.0.Alpha1, < 5.0.6.Final
>= 6.0.0.Beta1, < 6.2.3.Final
4.7.8.Final
5.0.6.Final
6.2.3.Final

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-2c6g-pfx3-w7h8. This link is maintained to preserve external references.

Original Description

In RESTEasy the insecure File.createTempFile() is used in the DataSourceProvider, FileProvider and Mime4JWorkaround classes which creates temp files with insecure permissions that could be read by a local user.

References

Published by the National Vulnerability Database Feb 17, 2023
Published to the GitHub Advisory Database Feb 18, 2023
Reviewed Feb 18, 2023
Withdrawn Jan 15, 2025
Last updated Jan 15, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-jrmh-v64j-mjm9

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.