CVE-2022-21619: 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: Security). 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
This is a low-severity Oracle Java SE and GraalVM Enterprise Edition flaw affecting integrity, not confidentiality or availability. It is hard to exploit, but could let an unauthenticated network attacker alter some data accessible to vulnerable Java components in specific deployment patterns.
Executive priority
Treat as routine patch management unless the organization depends on legacy Java sandboxing or exposed services using affected Security APIs. It does not justify emergency response based on the provided evidence, but should be included in normal Java update cycles.
Technical view
CVE-2022-21619 is a CWE-284 access-control issue in the Oracle Java SE Security component. Affected versions include Java SE 8u341, 8u345-perf, 11.0.16.1, 17.0.4.1, 19 and GraalVM EE 20.3.7, 21.3.3, 22.2.0. CVSS is 3.7 with high attack complexity and low integrity impact.
Likely exposure
Exposure is most likely where affected Java runtimes run untrusted sandboxed Java Web Start or applet code, or where services feed untrusted data into the affected Security APIs. Generic Java use is not enough to prove exposure.
Exploitation context
The provided sources do not show active exploitation, and this CVE is not marked KEV. Oracle describes exploitation as difficult, unauthenticated, network-accessible via multiple protocols, and limited to unauthorized update, insert, or delete access to some accessible data.
Researcher notes
Key scoping detail is Oracle’s note: affected deployments usually involve sandboxed Java clients running untrusted code, or API exposure through services supplying data to the Security component. The source bundle does not provide exploit details or proof of active exploitation.
Mitigation direction
Upgrade affected Oracle Java SE and GraalVM EE versions using Oracle CPU guidance.
Apply relevant Fedora, Gentoo, or NetApp vendor updates where those distributions or products are used.
Reduce or retire reliance on sandboxed Java Web Start and applet execution.
Limit untrusted data paths into Java Security component APIs where feasible.
Check vendor guidance for exact fixed versions before deployment.
Validation and detection
Inventory Java SE JDK, JRE, and GraalVM EE versions across endpoints and servers.
Flag affected versions listed by Oracle for remediation tracking.
Identify sandboxed applet or Java Web Start workloads that load untrusted code.
Review services that pass internet-originated data into Java Security APIs.
Confirm patched package levels using Oracle, Fedora, Gentoo, or NetApp 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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.