All reports
High

Borsh serialization of HashMap is non-canonical

Affected versions

Version ranges need review.

Rust / Cargohashbrown
Affected versions
>=0.15.0 <0.15.1
Fixed version
0.15.1
Rust / Cargohashbrown
Affected versions
>= 0.15.0, < 0.15.1
Fixed version
0.15.1

Description

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.

Links