high8.9No CVE yet
GHSA-wwq9-3cpr-mm53
Borsh serialization of HashMap is non-canonical
Impact
The borsh serialization of the HashMap did not follow the borsh specification. It potentially produced non-canonical encodings dependent on insertion order. It also did not perform canonicty checks on decoding. This can result in consensus splits and cause equivalent objects to be considered distinct. This was patched in 0.15.1.
An attacker can exploit this over the network, without logging in, without any action by a user. If it succeeds: high risk of data being read, high risk of data or systems being changed, high risk of outages.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| rust | hashbrown | >= 0.15.0, < 0.15.1 | 0.15.1 |