google/rust-async-coap · Security
Data races in async-coap
- GHSA ID
- GHSA-9j8q-m9x5-9g6j
- CVE ID
- CVE-2020-36444
- Severity
- high
- Published
- Updated
- CVSS
- 8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CVSS v3
- 8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Description
An issue was discovered in the async-coap crate through 2020-12-08 for Rust.
Affected versions of this crate implement Send/Sync for ArcGuard<RC, T> with no trait bounds on RC. This allows users to send RC: !Send to other threads and also allows users to concurrently access Rc: !Sync from multiple threads.
This can result in memory corruption from data race or other undefined behavior caused by sending T: !Send to other threads (e.g. dropping MutexGuard<T> in another thread that didn't lock its mutex).
CWEs
- CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer
- CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
References
- https://nvd.nist.gov/vuln/detail/CVE-2020-36444 ↗
- https://rustsec.org/advisories/RUSTSEC-2020-0124.html ↗
- https://github.com/google/rust-async-coap/issues/33 ↗
- https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/async-coap/RUSTSEC-2020-0124.md ↗
- https://github.com/advisories/GHSA-9j8q-m9x5-9g6j ↗