Unsafe Accessor
Approved changes feed: RSS · Atom
cpe:2.3:a:unsafe_accessor_project:unsafe_accessor:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Unsafe Accessor Project (5626a416-0930-595e-bac1-3e1f26c28d82) |
|---|---|
| Product | Unsafe Accessor (c57008df-25c1-5d0c-88f7-39cd285df3b0) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/karlatemp/unsafeaccessor |
purl2cpe | 2026-06-01 10:12:45.839241 |
pkg:maven/io.github.karlatemp/unsafe-accessor |
purl2cpe | 2026-06-01 10:12:45.839245 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-31139 |
vulnerable | 2026-06-08 05:43:40.273547 |
No security checking for UnsafeAccess.getInstance() in UnsafeAccessor
MEDIUM (5.9)
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.
Published: 2022-07-11T18:25:11.000Z
Updated: 2025-04-23T18:03:51.382Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.