CVE-2022-39399: 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: Networking). Supported versions that are affected are Oracle Java SE: 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 HTTP 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 does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). 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-39399 is a low-severity Oracle Java networking flaw affecting specific Java SE and GraalVM Enterprise versions. The main business concern is integrity: an attacker could alter some accessible data, but the attack is difficult and mainly relevant to sandboxed Java Web Start or applet deployments running untrusted code.
Executive priority
Treat this as routine patch governance, not an emergency, unless the organization still depends on sandboxed Java client technology running untrusted code. Prioritize discovery of those legacy workflows and ensure affected runtimes are updated through vendor-supported channels.
Technical view
Oracle describes this as a CWE-284 access-control issue in the Networking component. It is remotely reachable over HTTP without authentication, has high attack complexity, and affects integrity only. Oracle states it applies to sandboxed client-style Java deployments running untrusted code, not typical servers running only trusted administrator-installed code.
Likely exposure
Exposure is most likely where affected Java SE or GraalVM Enterprise versions support sandboxed Java Web Start applications or applets that load untrusted internet-sourced code. Standard server-side Java deployments running trusted code are explicitly excluded by Oracle's note.
Exploitation context
The bundle provides no evidence of active exploitation, and KEV status is false. Oracle rates exploitation as difficult, with CVSS 3.1 score 3.7 and high attack complexity. The stated impact is limited unauthorized update, insert, or delete access to some accessible data.
Researcher notes
Key constraints are the deployment note and limited integrity impact. Do not generalize this to all Java server workloads. The public bundle does not provide exploit details, active exploitation evidence, or explicit fixed version numbers beyond vendor advisory references.
Mitigation direction
Apply Oracle CPU Oct 2022 guidance for affected Java SE and GraalVM Enterprise versions.
Update downstream packages using Fedora, Gentoo, NetApp, or other applicable vendor advisories.
Reduce or retire sandboxed Java Web Start and applet workflows that run untrusted code.
If patch status is unclear, check the current vendor advisory before accepting residual risk.
Validation and detection
Inventory Java SE and GraalVM Enterprise runtime versions against the affected version list.
Identify any Java Web Start or applet use that loads untrusted code from the internet.
Confirm vendor packages include fixes referenced by Oracle or the downstream distribution advisory.
Document why server-only trusted-code Java deployments are considered outside this CVE scope.
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.