OMGeeky/advisory-db
1
0
Fork 0
mirror of https://github.com/OMGeeky/advisory-db.git synced 2026-02-23 15:38:27 +01:00
Code Issues Packages Projects Releases Wiki Activity
Files
0fcce3f7cbbc76da50ab0d778399bf85dc141834
advisory-db/crates/borsh/RUSTSEC-2023-0033.md
Alexis Mousset 84c633df9c Update aliases from GHSA OSV export (#1693)
2023-06-13 15:10:24 +02:00

930 B
Raw Blame History 

[advisory]
id = "RUSTSEC-2023-0033"
package = "borsh"
date = "2023-04-12"
url = "https://github.com/near/borsh-rs/issues/19"
references = ["https://github.com/near/borsh-rs/pull/136"]
informational = "unsound"
categories = ["memory-corruption"]
aliases = ["GHSA-fjx5-qpf4-xjf2"]

[affected]
[versions]
patched = []

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 not ZST are used for serialization, then you are not affected by this issue.