CVE-2020-36207

An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.

An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.

`aovec::Aovec<T>` is a vector type that implements `Send` and `Sync` for all types `T`. This allows non-Send types such as `Rc` and non-Sync types such as `Cell` to be used across thread boundaries which can trigger undefined behavior and memory corruption.

An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.

Se detectó un problema en la crate aovec hasta el 10-12-2020 para Rust.&#xa0;Debido a que Aovec(T) no posee límites en su atributo Send o atributo Sync, una carrera de datos y corrupción de la memoria puede ocurrir