Java SE JDK and JRE: Improper Access Control
CVE-2024-20952 is a high-severity improper access control vulnerability in Java SE JDK and JRE from Oracle, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Java SE JDK and JRE versions: Oracle Java SE:8u391; Oracle Java SE:8u391-perf; Oracle Java SE:11.0.21, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.92% chance of exploitation within 30 days, higher than 61% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Openjdk to 11.0.24 or 17.0.10 or 21.0.2, whichever matches your release line, or a later version.
- Read the advisory on oracle.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Oracle | Java SE JDK and JRE | Oracle Java SE:8u391; Oracle Java SE:8u391-perf; Oracle Java SE:11.0.21; Oracle Java SE:17.0.9; Oracle Java SE:21.0.1; Oracle GraalVM for JDK:17.0.9; Oracle GraalVM for JDK:21.0.1; Oracle GraalVM Enterprise Edition:20.3.12; and 2 more ranges | Not stated |
| Oracle | Openjdk | 11 up to, but not including, 11.0.24; 17 up to, but not including, 17.0.10; 21 up to, but not including, 21.0.2; 8 | 11.0.24, 17.0.10, 21.0.2 |
| Oracle | Graalvm | 20.3.12; 21.3.8; 22.3.4 | Not stated |
| Oracle | Graalvm For JDK | 17.0.9; 21.0.1 | Not stated |
| Oracle | JDK | 1.8.0; 11.0.21; 17.0.9; 21.0.1 | Not stated |
| Oracle | JRE | 1.8.0; 11.0.21; 17.0.9; 21.0.1 | Not stated |
| NetApp | Cloud Insights Acquisition Unit | Not specified in the record | Not stated |
| NetApp | Cloud Insights Storage Workload Security Agent | Not specified in the record | Not stated |
| NetApp | Oncommand Insight | Not specified in the record | Not stated |
| Debian | Debian Linux | 10.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (oracle.com).
Official description
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Security). Supported versions that are affected are Oracle Java SE: 8u391, 8u391-perf, 11.0.21, 17.0.9, 21.0.1; Oracle GraalVM for JDK: 17.0.9, 21.0.1; Oracle GraalVM Enterprise Edition: 20.3.12, 21.3.8 and 22.3.4. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, 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 7.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2024/01/msg00023.htmlMailing List, Third Party Advisory
- security.netapp.com/advisory/ntap-20240201-0002/Third Party Advisory
Other references
Other vulnerabilities in Java SE JDK and JRE
- 7.4 High severity
- 7.5 High severity
- 7.4 High severity
Recent Improper Access Control vulnerabilities
- 8.3 High severity
- 7.4 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.