Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. signal-simple
  4. ›
  5. CVE-2020-36446

CVE-2020-36446: Data races in signal-simple

August 25, 2021 (updated June 13, 2023)

Affected versions of this crate unconditionally implement Send/Sync for SyncChannel. SyncChannel doesn’t provide access to &T but merely serves as a channel that consumes and returns owned T.

Users can create UB in safe Rust by sending T: !Send to other threads with SyncChannel::send/recv APIs. Using T = Arc<Cell<_> allows to create data races (which can lead to memory corruption), and using T = MutexGuard allows to unlock a mutex from a thread that didn’t lock the mutex.

References

  • github.com/advisories/GHSA-36cg-4jff-5863
  • github.com/kitsuneninetails/signal-rust/issues/2
  • nvd.nist.gov/vuln/detail/CVE-2020-36446
  • raw.githubusercontent.com/rustsec/advisory-db/main/crates/signal-simple/RUSTSEC-2020-0126.md
  • rustsec.org/advisories/RUSTSEC-2020-0126.html

Code Behaviors & Features

Detect and mitigate CVE-2020-36446 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions up to 0.1.1

Solution

Unfortunately, there is no solution available yet.

Impact 8.1 HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Learn more about CVSS

Weakness

  • 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')

Source file

cargo/signal-simple/CVE-2020-36446.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 14 May 2025 12:15:10 +0000.