Deserialize implementation for
VecStorage did not maintain the invariant that the number of elements must equal
nrows * ncols. Deserialization of specially crafted inputs could allow memory access beyond allocation of the vector.
This flaw was introduced in v0.11.0 (
086e6e) due to the addition of an automatically derived implementation of
MatrixVec was later renamed to
VecStorage in v0.16.13 (
0f66403) and continued to use the automatically derived implementation of
This flaw was corrected in commit
5bff536 by returning an error during deserialization if the number of elements does not exactly match the expected size.
Advisory available under CC0-1.0