Security readout for executives and security teams
Plain-English summary
CVE-2022-31139 affects the Java UnsafeAccessor library when its access-limiting feature is enabled. In affected versions, untrusted code may bypass intended limits and reach UnsafeAccessor functionality, creating a confidentiality risk. The vendor patched this in version 1.7.0.
Executive priority
Prioritize remediation for Java services that run untrusted code or depend on UnsafeAccessor to enforce isolation. For ordinary applications without AccessLimiter, the source material indicates no impact. Upgrade during the next controlled dependency patch cycle unless the library protects a trust boundary.
Technical view
UnsafeAccessor versions 1.4.0 through before 1.7.0 fail to enforce SecurityCheck.AccessLimiter for UnsafeAccess.getInstance(). When AccessLimiter is configured, untrusted code can access UA without the intended restrictions, even when UA is loaded as a named module. The issue is classified as CWE-200.
Likely exposure
Exposure is narrow: Java applications using Karlatemp UnsafeAccessor >=1.4.0 and <1.7.0, with SecurityCheck.AccessLimiter configured, and running untrusted code in the relevant JVM context. The advisory states users without AccessLimiter configured are not affected.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. The CVSS 3.1 score is 5.9, with high attack complexity and confidentiality impact only. Treat this as important where Java plugin, scripting, or sandbox boundaries rely on UnsafeAccessor limits.
Researcher notes
Key condition is AccessLimiter being set; do not broaden impact to all UnsafeAccessor users. The weakness is an access-control failure around UnsafeAccess.getInstance(), producing confidentiality exposure. Public sources identify the fixed release and commit, but do not provide evidence of exploitation.
Mitigation direction
- Upgrade Karlatemp UnsafeAccessor to version 1.7.0 or later.
- Identify applications using UnsafeAccessor versions >=1.4.0 and <1.7.0.
- Review whether SecurityCheck.AccessLimiter is configured in affected applications.
- Check vendor advisory and release notes for any deployment-specific guidance.
Validation and detection
- Confirm the resolved UnsafeAccessor version in each Java application dependency tree.
- Verify whether SecurityCheck.AccessLimiter is enabled in application configuration or code.
- Prioritize systems that execute plugins, scripts, extensions, or other untrusted JVM code.
- Retest security-boundary assumptions after upgrading to version 1.7.0 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31139 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Karlatemp/UnsafeAccessor/security/advisories/GHSA-cr6p-23cf-w9g9CVE reference · x_refsource_CONFIRM
- https://github.com/Karlatemp/UnsafeAccessor/commit/4ef83000184e8f13239a1ea2847ee401d81585fdCVE reference · x_refsource_MISC
- https://github.com/Karlatemp/UnsafeAccessor/releases/tag/1.7.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.