Skip to content

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

Moderate severity GitHub Reviewed Published Jul 11, 2022 in Karlatemp/UnsafeAccessor • Updated Jul 24, 2023

Package

maven io.github.karlatemp:unsafe-accessor (Maven)

Affected versions

>= 1.4.0, < 1.7.0

Patched versions

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

References

@Karlatemp Karlatemp published to Karlatemp/UnsafeAccessor Jul 11, 2022
Published by the National Vulnerability Database Jul 11, 2022
Published to the GitHub Advisory Database Jul 12, 2022
Reviewed Jul 12, 2022
Last updated Jul 24, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.114%
(46th percentile)

Weaknesses

CVE ID

CVE-2022-31139

GHSA ID

GHSA-cr6p-23cf-w9g9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.