CVE-2022-21624: Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component...
Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JNDI). Supported versions that are affected are Oracle Java SE: 8u341, 8u345-perf, 11.0.16.1, 17.0.4.1, 19; Oracle GraalVM Enterprise Edition: 20.3.7, 21.3.3 and 22.2.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. CVSS 3.1 Base Score 3.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N).
Security readout for executives and security teams
Plain-English summary
CVE-2022-21624 is a low-severity Oracle Java JNDI vulnerability. In specific Java or GraalVM deployments, a remote unauthenticated attacker could cause unauthorized changes to some accessible data. Oracle says exploitation is difficult. Treat it as routine patching, with priority for internet-facing Java services handling untrusted input.
Executive priority
Address in the normal security patch cycle, sooner for internet-facing Java services or systems relying on Java sandbox boundaries. There is no source-backed indication of active exploitation, but affected runtimes are common enough to justify prompt inventory and update validation.
Technical view
The issue affects Oracle Java SE and Oracle GraalVM Enterprise Edition JNDI components in listed versions. It is mapped to CWE-502 and has CVSS 3.1 score 3.7, with network attack vector, high complexity, no privileges, no user interaction, and low integrity impact only.
Likely exposure
Exposure is most relevant where affected Java or GraalVM versions run sandboxed untrusted code, Java Web Start/applets, or services that pass externally supplied data into JNDI-related APIs. Downstream advisories from Fedora, Gentoo, and NetApp indicate ecosystem packaging or product dependency considerations.
Exploitation context
The bundle does not cite active exploitation, and KEV status is false. The vulnerability is remotely reachable over multiple protocols but difficult to exploit. Documented impact is limited to unauthorized update, insert, or delete access to some accessible data.
Researcher notes
Evidence is strongest for affected versions, component, CVSS, and general impact. The provided bundle does not include exploit details or exact fixed version mappings, so validation should rely on vendor advisory checks and runtime inventory rather than assumptions about applications.
Mitigation direction
Review Oracle CPU October 2022 guidance for corrected Java and GraalVM builds.
Apply relevant downstream Fedora, Gentoo, or vendor package updates where applicable.
Prioritize Java services that expose JNDI-influenced behavior to untrusted network input.
Reduce reliance on sandboxed execution of untrusted Java code where possible.
Check NetApp guidance if affected Java components are embedded in managed products.
Validation and detection
Inventory Oracle Java SE and GraalVM Enterprise Edition versions across servers and endpoints.
Identify Java Web Start, applet, or sandboxed untrusted-code usage.
Review services that pass external data into JNDI-related APIs.
Confirm upgraded runtime versions against Oracle and distributor advisories.
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 · medium confidence lookup
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-502 · source CWE mapping
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.