UnsafeAccessor 1.4.0 until 1.7.0 has no security checking for UnsafeAccess.getInstance()

高 7.5CVE-2022-31139 · GHSA-cr6p-23cf-w9g9 · 11/07/2022 公開 · 17/06/2026 更新

要点

CVE-2022-31139 は io.github.karlatemp:unsafe-accessor, unsafe accessor (unsafe accessor project) に影響する深刻度「高」 (CVSS 7.5) の脆弱性です。
今後30日間に悪用される確率（EPSS）：1.2%（全脆弱性の 67.8% より高い）。
対処：1.7.0 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
io.github.karlatemp:unsafe-accessor Maven	`≥ 1.4.0, < 1.7.0`	`1.7.0`
unsafe accessor unsafe_accessor_project	`≥ 1.4.0, < 1.7.0`	`1.7.0`

概要

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

NVD の説明

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.