enum-map
Affected
- introduced
3.0.0-0.gat.0, fixed3.1.0(semver)
Fixed versions
3.1.0
Fix
- Fixed version
3.1.0cargo update -p enum-map --precise 3.1.0
Advisory
Also known as: None
Enum trait allows type confusion when manually implemented
Affected versions of this crate did not require the element type of the Array associated type in the Enum trait to match the array's generic parameter V.
This can result in type confusion, and consequently memory corruption, when a manual Enum implementation declares an Array<V> whose elements are not actually of type V:
struct IntentionallyWrong;
impl Enum for IntentionallyWrong {
type Array<V> = [String; 4];
fn from_usize(_: usize) -> Self {
IntentionallyWrong
}
fn into_usize(self) -> usize {
0
}
}
enum_map! { IntentionallyWrong => 42 };
The flaw was corrected in commit 7a8b815432 by adding a Value = V bound to the Array type in the Enum trait.
Not rated by the source.
3.0.0-0.gat.0, fixed 3.1.0 (semver)3.1.0
3.1.0cargo update -p enum-map --precise 3.1.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0