GitHub Advisoryadvisory · Maven

GHSA-cr6p-23cf-w9g9 UnsafeAccessor 1.4.0 until 1.7.0 has no security checking for UnsafeAccess.getInstance()

MEDIUM Published 2022-07-12 Modified 2022-07-21 Official page ↗
Aliases
CVE-2022-31139
Ecosystem
Maven
Packages
io.github.karlatemp:unsafe-accessor
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-200, CWE-863
Reviewed
2022-07-12

Affected packages

• Maven io.github.karlatemp:unsafe-accessor: >= 1.4.0, < 1.7.0 → fixed in 1.7.0

Description

Overview Affected versions have no limit to using unsafe-accessor. Can be ignored if `SecurityCheck.AccessLimiter` not setup Details If UA was loaded as a named module, the internal data of UA will be protected by JVM and others can only access UA via UA's standard api. Main application can setup `SecurityCheck.AccessLimiter` for UA to limit accesses to UA. Untrusted code can access UA without lmitation in affected versions even UA was loaded as a named module. References The commit to fix

Related

Alias · CVE (1)

  • CVE-2022-31139 UnsafeAccessor (UA) is a bridge to access jdk.internal.misc.Unsafe & sun.misc.Unsafe. vulnerability

Weakness · CWE (2)

  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness
  • CWE-863 Incorrect Authorization weakness

References