Description
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 you are not using ZST for serialization, then you are not affected by this issue.
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| crates.io | borsh | < 1.0.0-alpha.1 | 1.0.0-alpha.1 | GHSA-fjx5-qpf4-xjf2 |
| crates.io | borsh | >= 0.0.0-0, < 0.10.4 · >= 0.11.0-0, < 1.0.0-alpha.1 | 0.10.4, 1.0.0-alpha.1 | RUSTSEC-2023-0033 |