RUSTSEC-2023-0033

Source

https://rustsec.org/advisories/RUSTSEC-2023-0033

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2023-0033.json

Aliases

GHSA-fjx5-qpf4-xjf2

Published

2023-04-12T12:00:00Z

Modified

2023-11-08T04:19:03.348979Z

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

Affected packages

crates.io / borsh

Package

Name: borsh

Affected ranges

Type: SEMVER
Events: Introduced

0.0.0-0

Fixed

1.0.0-alpha.1

Ecosystem specific

{
    "affects": {
        "os": [],
        "functions": [],
        "arch": []
    }
}

Database specific

{
    "cvss": null,
    "informational": "unsound",
    "categories": [
        "memory-corruption"
    ]
}