EUVD-2021-1918

Malware in sbrugna...

CVE-2021-28032

An issue was discovered in the nanoarena crate before 0.5.2 for Rust. There is an aliasing violation in splitat because two mutable references can exist for the same element, if Borrow behaves in certain ways. This can have a resultant out-of-bounds write or use-after-free...

Use after free in nano_arena

Affected versions of this crate assumed that Borrow was guaranteed to return the same value on .borrow. The borrowed index value was used to retrieve a mutable reference to a value. If the Borrow implementation returned a different index, the split arena would allow retrieving the index as a...

GHSA-WP34-MQW5-JJ85 Use after free in nano_arena

Affected versions of this crate assumed that Borrow was guaranteed to return the same value on .borrow. The borrowed index value was used to retrieve a mutable reference to a value. If the Borrow implementation returned a different index, the split arena would allow retrieving the index as a...

Unspecified Vulnerability in Rust (CNVD-2021-17262)

Rust is a general-purpose, compiled programming language from the Mozilla Foundation. A security vulnerability exists in nanoarena crate before 0.5.2 for Rust, which can be exploited by attackers to cause a write out-of-bounds or use-after-free...

CVE-2021-28032

An issue was discovered in the nanoarena crate before 0.5.2 for Rust. There is an aliasing violation in splitat because two mutable references can exist for the same element, if Borrow behaves in certain ways. This can have a resultant out-of-bounds write or use-after-free...

CVE-2021-28032

The CVE concerns the Rust crate nano_arena before 0.5.2. A flaw in the split_at logic allows two mutable references to the same element when Borrow behaves in certain ways, creating a potential for memory safety issues such as an out-of-bounds write or use-after-free. The issue is rooted in alias...

CVE-2021-28032

An issue was discovered in the nanoarena crate before 0.5.2 for Rust. There is an aliasing violation in splitat because two mutable references can exist for the same element, if Borrow behaves in certain ways. This can have a resultant out-of-bounds write or use-after-free...