borsh
Affected
- introduced
0, fixed1.0.0-alpha.1(semver)
Fixed versions
1.0.0-alpha.1
Fix
- Fixed version
1.0.0-alpha.1cargo update -p borsh --precise 1.0.0-alpha.1
Advisory
Also known as: RUSTSEC-2023-0033
Parsing borsh messages with ZST which are not-copy/clone is unsound
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.
Medium Basis: The source's own band: MODERATE
0, fixed 1.0.0-alpha.1 (semver)1.0.0-alpha.1
1.0.0-alpha.1cargo update -p borsh --precise 1.0.0-alpha.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0