LiveActive security incident?Get immediate response
CVE Record

CVE-2023-0482: In RESTEasy the insecure File.createTempFile() is used in the DataSourceProvider, FileProvider and Mime4JWo...

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.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

RESTEasy created temporary files with permissions that could let another local user read them. The business impact is potential exposure of sensitive data processed through affected RESTEasy providers. This is not a remote takeover issue in the cited sources, but it matters on shared hosts or systems with multiple local users.

Executive priority

Treat this as a moderate confidentiality risk. Prioritize systems that process sensitive files or data on shared servers, developer workstations, appliances, or environments where local users have access.

Technical view

CVE-2023-0482 is a CWE-378 insecure temporary file permissions issue in RESTEasy DataSourceProvider, FileProvider, and Mime4JWorkaround. CVSS 3.1 is 5.5 with local attack vector, low complexity, low privileges, no user interaction, and high confidentiality impact. The bundle states it is fixed in RESTEasy 4.7.8.Final.

Likely exposure

Exposure is most likely where applications or products bundle RESTEasy and process sensitive content through affected provider code. Exact affected version ranges are not fully stated in the provided bundle beyond the fixed release. NetApp published an advisory, so downstream bundled usage should be checked.

Exploitation context

No cited source or KEV entry supports active exploitation. Exploitation requires local access and low privileges on the affected system. The plausible outcome is reading temporary files created with insecure permissions, not integrity change or service disruption.

Researcher notes

The key evidence is narrow: insecure File.createTempFile usage in three RESTEasy classes and a fixed release reference. Do not assume remote exploitability, broader product impact, or active exploitation without additional vendor evidence.

Mitigation direction

  • Upgrade RESTEasy to 4.7.8.Final or a later vendor-supported fixed release.
  • Check downstream vendor advisories for products that bundle RESTEasy, including NetApp guidance.
  • Reduce local multi-user exposure on systems running affected applications until fixed.
  • Review application handling of sensitive data written through RESTEasy providers.

Validation and detection

  • Inventory RESTEasy versions in application dependencies, SBOMs, and bundled products.
  • Confirm deployed runtime artifacts match RESTEasy 4.7.8.Final or later fixed builds.
  • Identify systems where local users share hosts with affected RESTEasy workloads.
  • Review vendor advisories for any product-specific affected status and remediation notes.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-378: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-0482 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-0482Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aRESTEasyFixed in RESTEasy 4.7.8.FinalListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-378 · source CWE mapping

Creation of Temporary File With Insecure Permissions

Creation of Temporary File With Insecure Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.