GHSA-cr6p-23cf-w9g9

    Dashboard / Vulnerabilities / GHSA-cr6p-23cf-w9g9

    GHSA-cr6p-23cf-w9g9

    Published: 12 Jul 2022Last Modified: 16 Feb 2024

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

    Details: ### 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](https://github.com/Karlatemp/UnsafeAccessor/commit/4ef83000184e8f13239a1ea2847ee401d81585fd)

    Affected packages

    Package

    Name: io.github.karlatemp:unsafe-accessor

    Purl: pkg:maven/io.github.karlatemp/unsafe-accessor

    Affected ranges

    Type: ECOSYSTEM

    Events:

    Introduced- 1.4.0
    Fixed -1.7.0

    Affected versions

    1.4.0

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    GHSA-cr6p-23cf-w9g9 | CVE-DB