همهٔ گزارش‌ها
زیاد

Race Condition in tokio

متن اصلی

نسخه‌های متأثر

بازه‌ها نیاز به بررسی دارند.

Rust / Cargotokio
نسخه‌های متأثر
>= 0.1.14, < 1.8.4
نسخهٔ اصلاح‌شده
1.8.4
Rust / Cargotokio
نسخه‌های متأثر
>= 1.9.0, < 1.13.1
نسخهٔ اصلاح‌شده
1.13.1
Rust / Cargotokio
نسخه‌های متأثر
>=0.1.14 <1.8.4 || >=1.9.0 <1.13.1
نسخهٔ اصلاح‌شده
1.13.1 · 1.8.4

بهره‌برداری

CVE-2021-45710

احتمال بهره‌برداری در ۳۰ روز آینده: 1.24%

FIRST EPSS · ۱۴۰۵/۰۸/۲۹

شرح آسیب‌پذیری

If a tokio::sync::oneshot channel is closed (via the oneshot::Receiver::close method), a data race may occur if the oneshot::Sender::send method is called while the corresponding oneshot::Receiver is awaited or calling try_recv.

When these methods are called concurrently on a closed channel, the two halves of the channel can concurrently access a shared memory location, resulting in a data race. This has been observed to cause memory corruption.

Note that the race only occurs when both halves of the channel are used after the Receiver half has called close. Code where close is not used, or where the Receiver is not awaited and try_recv is not called after calling close, is not affected.

پیوندها