pypi package report

Is ubi-reader safe?

2 known vulnerabilities, worst severity MODERATE.

// reach

3 direct dependencies

1 carry known advisories, worst HIGH

0 packages depend on it

an advisory here reaches each of them

    Create a free accountfor every dependency path, dependent and what to upgrade
    // ai model usage

    No published models are known to use this package.


    cvss
    5.5
    medium

    CVSS v3.1 base score out of 10

    epss
    0.39%
    low

    chance of exploitation in 30 days, 34th percentile of all CVEs

    xyz score
    not scored

    CyberXYZ composite out of 10

    fig. 01 — GHSA-vp2x-3mc3-3cj4, the advisory selected below

    // 2 advisories

    GHSA-vp2x-3mc3-3cj4

    MODERATEGitHub ratingCVE-2023-0591

    ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory). This is due to the fact that a node name (dent_node.name) is considered trusted and joined to the extraction directory path during processing, then the node content is written to that joined path. By crafting a malicious UBIFS file with node names holding path traversal payloads (e.g. ../../tmp/outside.txt), it's possible to force ubi_reader to write outside of the extraction directory. This issue affects ubi-reader before 0.8.5.

    // cvss v3.1 vector

    CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

    Attack vector
    Local
    Attack complexity
    Low
    Privileges required
    None
    User interaction
    Required
    Scope
    Unchanged
    Confidentiality
    None
    Integrity
    High
    Availability
    None

    Checked 2026-11-08 at 00:37 UTC. The most recent advisory here was published 2023-01-31. Updated continuously from NVD, GHSA, OSV and CNA feeds.

    Think a verdict here is wrong? Tell us — we respond within 2 business days.