CVE-2022-31139
Summary
| CVE | CVE-2022-31139 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2022-07-11 19:15:00 UTC |
| Updated | 2023-07-24 13:16:00 UTC |
| 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. |
Risk And Classification
Problem Types: CWE-863
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Unsafe Accessor Project | Unsafe Accessor | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| NO Security checking for UnsafeAccess.getInstance() · Advisory · Karlatemp/UnsafeAccessor · GitHub | CONFIRM | github.com | |
| Release 1.7.0 · Karlatemp/UnsafeAccessor · GitHub | MISC | github.com | |
| Fix UnsafeAccess perm checking · Karlatemp/UnsafeAccessor@4ef8300 · GitHub | MISC | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.