MEDIUM
GHSA-7v4j-8wvr-v55r
`array!` macro is unsound when its length is impure constant
Details
Affected versions of this crate did substitute the array length provided by an user at compile-time multiple times.
When an impure constant expression is passed as an array length (such as a result of an impure procedural macro), this can result in the initialization of an array with uninitialized types, which in turn can allow an attacker to execute arbitrary code.
The flaw was corrected in commit [d5b63f72](https://github.com/xfix/array-macro/commit/d5b63f72090f3809c21ac28f9cfd84f12559bf7d) by making sure that array length is substituted just once.
Are you affected?
Enter the version of the package you're using.
Affected packages
crates.io/array-macro
Introduced in:
2.1.0Fixed in: 2.1.2Upgrade array-macro to 2.1.2 or newer (ecosystem crates.io).
References
- https://github.com/xfix/array-macro/commit/d5b63f72090f3809c21ac28f9cfd84f12559bf7d[WEB]
- https://github.com/rustsec/advisory-db/blob/main/crates/array-macro/RUSTSEC-2022-0017.md[WEB]
- https://github.com/xfix/array-macro[PACKAGE]
- https://gitlab.com/KonradBorowski/array-macro/-/issues/5[WEB]
- https://rustsec.org/advisories/RUSTSEC-2022-0017.html[WEB]