Skip to content
Fencer Intel
high 8.1

CVE-2021-45710 json

Race Condition in tokio

published 4y ago modified 4mo ago also GHSA-fg7r-2g4j-5cgr , RUSTSEC-2021-0124 , EUVD-2022-0582

cvss
8.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

An issue was discovered in the tokio crate before 1.8.4, and 1.9.x through 1.13.x before 1.13.1, for Rust. In certain circumstances involving a closed oneshot channel, there is a data race and memory corruption.

Patch / fix

  • crates.io tokio 1.8.4, 1.13.1
  • tokio tokio 1.8.4, 1.13.1
  • rust-tokio Debian 14, Debian 13, Debian 12 1.15.0-1

debian advisories DEBIAN-CVE-2021-45710

  • sccache SLE Module for Development Tools 15 SP5, SLE Module for Development Tools 15 SP4, openSUSE Leap 15.5 +1 more 0.4.2~3-150400.3.3.1
  • 389-ds SLE Module for Server Applications 15 SP3, openSUSE Leap 15.3 1.4.4.19~git59.136fc84-150300.3.27.1
  • sccache SLE Module for Development Tools 15 SP3, openSUSE Leap 15.3 0.3.0~git5.14a4b8b-150300.7.9.1
  • 389-ds SLE Module for Server Applications 15 SP4, openSUSE Leap 15.4 2.0.16~git56.d15a0a7-150400.3.15.1
  • rustup SLE Module for Development Tools 15 SP3, openSUSE Leap 15.3 1.25.1~0-150300.7.13.2

suse advisories SUSE-SU-2023:3526-1SUSE-SU-2022:4124-1SUSE-SU-2022:4073-1SUSE-SU-2022:3996-1SUSE-SU-2022:3949-1

  • kanidm Package Hub 15 SP6, openSUSE Leap 15.6 1.3.3~git0.f075d13-bp156.4.1
  • greetd openSUSE Tumbleweed 0.8.0-2.1
  • rustscan openSUSE Tumbleweed 2.0.1+0-1.1
  • rustup openSUSE Tumbleweed 1.24.3~git1.0a74fef5-2.1
  • sccache openSUSE Tumbleweed 0.2.15~git0.6b6d2f7-8.1
  • tuigreet openSUSE Tumbleweed 0.7.1-3.1
  • cargo-c openSUSE Tumbleweed 0.8.1~git0.cce1b08-2.1
  • spotifyd openSUSE Tumbleweed 0.3.3-2.1

opensuse advisories openSUSE-SU-2024:0294-1openSUSE-SU-2024:11710-1openSUSE-SU-2024:11714-1openSUSE-SU-2024:11715-1openSUSE-SU-2024:11716-1openSUSE-SU-2024:11717-1

Is CVE-2021-45710 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-45710 updated cvss 7.3

tokio: Race leads to panic in oneshot::Sender::send()

  • Red Hat Enterprise Linux 8 nispor, 389-ds-base, cockpit-389-ds, python3-lib389, python3-nispor, 389-ds-base-libs, +2 more Red Hat Enterprise Linux 9 nispor, 389-ds-base, python3-lib389, python3-nispor, 389-ds-base-libs, 389-ds-base-snmp, +1 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 5.1 AV:N/AC:H/Au:N/C:P/I:P/A:P
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
crates.io tokio
>=0.1.14, <1.8.4
>=1.9.0, <1.13.1
1.8.4
1.13.1

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.