RUSTSEC-2023-0033

    Dashboard / Vulnerabilities / RUSTSEC-2023-0033

    RUSTSEC-2023-0033

    Published: 12 Apr 2023Last Modified: 23 Sept 2024

    Summary: Parsing borsh messages with ZST which are not-copy/clone is unsound

    Details: Affected versions of borsh cause undefined behavior when zero-sized-types (ZST) are parsed and the Copy/Clone traits are not implemented/derived. For instance if 1000 instances of a ZST are deserialized, and the ZST is not copy (this can be achieved through a singleton), then accessing/writing to deserialized data will cause a segmentation fault. There is currently no way for borsh to read data without also providing a Rust type. Therefore, if not ZST are used for serialization, then you are not affected by this issue.

    References: https://crates.io/crates/borsh, https://rustsec.org/advisories/RUSTSEC-2023-0033.html, https://github.com/near/borsh-rs/issues/19, https://github.com/near/borsh-rs/pull/136

    Affected packages

    Package

    Name: borsh

    Purl: pkg:cargo/borsh

    Affected ranges

    Type: SEMVER

    Events:

    Introduced- 0.0.0-0
    Fixed -0.10.4

    Affected versions

    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
    RUSTSEC-2023-0033 | CVE-DB