Vulnerability in Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 8u503-perf, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1, 27; Oracle GraalVM for JDK: 17.0.20.1 and 21.0.12.1; Oracle GraalVM Enterprise Edition: 21.3.19.1.1. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle Java SE executes to compromise Oracle Java SE. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also 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. CVSS 3.1 Base Score 4.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N).
Weakness
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Build of OpenJDK 17.0.21 | RedHat | java-17-openjdk-portable | * |
| Red Hat Enterprise Linux 10 | RedHat | java-25-openjdk-1:25.0.5.0.8-1.0.el10 | * |
| Red Hat Enterprise Linux 8 | RedHat | java-17-openjdk-1:17.0.21.0.9-2.1.el8 | * |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | RedHat | java-17-openjdk-1:17.0.21.0.9-2.1.el8 | * |
| Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On | RedHat | java-17-openjdk-1:17.0.21.0.9-2.1.el8 | * |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | RedHat | java-17-openjdk-1:17.0.21.0.9-2.1.el8 | * |
| Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On | RedHat | java-17-openjdk-1:17.0.21.0.9-2.1.el8 | * |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | RedHat | java-17-openjdk-1:17.0.21.0.9-2.1.el8 | * |
| Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions | RedHat | java-17-openjdk-1:17.0.21.0.9-2.1.el8 | * |
| Red Hat Enterprise Linux 9 | RedHat | java-25-openjdk-1:25.0.5.0.8-1.0.el9 | * |
| Openjdk-13 | Ubuntu | esm-apps/focal | * |
| Openjdk-16 | Ubuntu | esm-apps/focal | * |
| Openjdk-18 | Ubuntu | jammy | * |
| Openjdk-27 | Ubuntu | upstream | * |
| Openjdk-9 | Ubuntu | esm-apps-legacy/xenial | * |
Potential Mitigations
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
- Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
- For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
- One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.