CVE-2022-21549: 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: Libraries). Supported versions that are affected are Oracle Java SE: 17.0.3.1; Oracle GraalVM Enterprise Edition: 21.3.2 and 22.1.0. Easily exploitable 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 5.3 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).
Security readout for executives and security teams
Plain-English summary
CVE-2022-21549 is a medium-severity Oracle Java and GraalVM issue that can let an unauthenticated network attacker alter some accessible data. Business risk is highest where affected Java versions run untrusted sandboxed code or expose the vulnerable library behavior through services that process attacker-supplied data.
Executive priority
Treat as a targeted remediation item, not an emergency, unless affected Java runtimes process untrusted code or external service data. Prioritize internet-facing services and legacy Java client workflows first, then close remaining inventory gaps through normal patch governance.
Technical view
The CVE is in Oracle Java SE and Oracle GraalVM Enterprise Edition Libraries and is associated with CWE-502. Affected versions listed are Java SE 17.0.3.1 and GraalVM Enterprise Edition 21.3.2 and 22.1.0. CVSS 3.1 is 5.3, with network attack vector, low complexity, no privileges, no user interaction, and low integrity impact.
Likely exposure
Exposure is most likely in affected Java or GraalVM deployments that run untrusted Java Web Start or applet code, rely on Java sandboxing, or pass untrusted service data into the affected library APIs. Ordinary Java installations may be lower risk if those conditions are absent.
Exploitation context
The source bundle does not show CISA KEV listing or other confirmed active exploitation. Oracle describes the issue as easily exploitable over multiple protocols without authentication, but the documented impact is limited to unauthorized update, insert, or delete access to some accessible data.
Researcher notes
The available evidence supports integrity-only impact and affected-version scoping, but does not include exploit details or a named vulnerable class/API. Validation should focus on runtime versioning, exposure conditions in Oracle’s note, and downstream vendor package status rather than exploit reproduction.
Mitigation direction
Apply Oracle July 2022 CPU guidance for affected Java and GraalVM versions.
Use Debian, Fedora, Gentoo, NetApp, or other vendor advisories for packaged deployments.
Inventory and retire Java SE 17.0.3.1 where still present.
Inventory and retire GraalVM EE 21.3.2 and 22.1.0 where still present.
Reduce reliance on sandboxed untrusted Java code where business processes allow.
Validation and detection
Confirm installed Java SE and GraalVM versions across servers, desktops, and build images.
Identify Java Web Start, applet, or sandboxed untrusted-code usage.
Review services that pass external input into Java library APIs.
Check vendor package status against Oracle, Debian, Fedora, Gentoo, and NetApp advisories.
Verify updated runtime versions after patching or package upgrades.
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.