CVE-2022-31139CWE-200

No security checking for UnsafeAccess.getInstance() in UnsafeAccessor

Medium · published July 11, 2022

CVSS v3.1
5.9
EPSS
1%
Percentile
67.3
In the wild
Unconfirmed
What it is

UnsafeAccessor (UA) is a bridge to access jdk.internal.misc.Unsafe & sun.misc.Unsafe. Normally, if UA is loaded as a named module, the internal data of UA is protected by JVM and others can only access UA via UA's standard API. The main application can set up `SecurityCheck.AccessLimiter` for UA to limit access to UA. Starting with version 1.4.0 and prior to version 1.7.0, when `SecurityCheck.AccessLimiter` is set up, untrusted code can access UA without limitation, even when UA is loaded as a named module. This issue does not affect those for whom `SecurityCheck.AccessLimiter` is not set up. Version 1.7.0 contains a patch.

The record
Technical detail
CVSS v3.1
5.9 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS v4.0
Not supplied
EPSS
0.01175 · 67.3th percentile
Weakness
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
Published
2022-07-11T18:25Z
EPSS history
Timeline
  • 11 JUL 18:25Z
    No security checking for UnsafeAccess.getInstance() in UnsafeAccessor
    cvelistv5