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.
References
Link | Resource |
---|---|
https://github.com/Karlatemp/UnsafeAccessor/releases/tag/1.7.0 | Release Notes Third Party Advisory |
https://github.com/Karlatemp/UnsafeAccessor/commit/4ef83000184e8f13239a1ea2847ee401d81585fd | Patch Third Party Advisory |
https://github.com/Karlatemp/UnsafeAccessor/security/advisories/GHSA-cr6p-23cf-w9g9 | Patch Third Party Advisory |
Configurations
Information
Published : 2022-07-11 12:15
Updated : 2022-07-18 09:01
NVD link : CVE-2022-31139
Mitre link : CVE-2022-31139
JSON object : View
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor
Products Affected
unsafe_accessor_project
- unsafe_accessor