Vulnerability · Published Jul 11, 2022 · Assigned by GitHub_M
CVE-2022-31139No security checking for UnsafeAccess.getInstance() in UnsafeAccessor
Medium 5.9
In plain English
A medium-severity information exposure in UnsafeAccessor from Karlatemp. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 1.2% (higher than 68% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Maven | io.github.karlatemp:unsafe-accessor | 1.7.0 | GHSA-cr6p-23cf-w9g9 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Karlatemp | UnsafeAccessor | >= 1.4.0, < 1.7.0 |
Weakness: CWE-200 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N