RUSTSEC-2021-0124

Source

https://rustsec.org/advisories/RUSTSEC-2021-0124

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2021-0124.json

Aliases

Published

2021-11-16T12:00:00Z

Modified

2023-11-08T04:07:23.239744Z

Summary

Data race when sending and receiving after closing a `oneshot` channel

Details

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.

See tokio#4225 for more details.

References

Affected packages

crates.io / tokio

Package

Name: tokio

Affected ranges

Type: SEMVER
Events: Introduced

0.1.14

Fixed

1.8.4

Introduced

1.9.0

Fixed

1.13.1

Ecosystem specific

{
    "affects": {
        "os": [],
        "functions": [
            "tokio::sync::oneshot::Receiver::close"
        ],
        "arch": []
    }
}

Database specific

{
    "cvss": null,
    "informational": null,
    "categories": [
        "memory-corruption",
        "thread-safety"
    ]
}