CVE-2020-36208

An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.

An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.

Affected versions of `conquer-once` implements `Sync` for its `OnceCell` type without restricting it to `Send`able types. This allows non-`Send` but `Sync` types such as `MutexGuard` to be sent across threads leading to undefined behavior and memory corruption in concurrent programs. The issue was fixed by adding a `Send` constraint to `OnceCell`.

Affected versions of conquer-once implements Sync for its OnceCell type without restricting it to Sendable types. This allows non-Send but Sync types such as MutexGuard to be sent across threads leading to undefined behavior and memory corruption in concurrent programs. The issue was fixed by adding a Send constraint to OnceCell.

Se detectó un problema en la crate conquer-once versiones anteriores a 0.3.2 para Rust. Un cruce de subprocesos puede ocurrir para un non-Send pero de tipo Sync, conllevando a una corrupción de la memoria