GHSA-8892-84wf-cg8f: SyncChannel<T> can move 'T !Send' To Other Threads Vulnerability

HIGH
Share
CVSS 8.1
CWE-362
Published
Advisory Summary

GHSA-8892-84wf-cg8f is a HIGH (CVSS 8.1) !send' to other threads vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting SyncChannel<T> can move 'T libraries in the crates.io ecosystem. The issue involves !send' to other threads. Remediation is available in the latest vendor maintenance releases.

GHSA-8892-84wf-cg8f at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-8892-84wf-cg8f
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected Product SyncChannel<T> can move 'T
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix GHSA-8892-84wf-cg8f

To remediate this vulnerability, upgrade all affected SyncChannel<T> can move 'T dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

signal-simple fixed: Latest secure release 
Upgrade signal-simple to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for signal-simple

How to Check if You Are Affected

To determine whether your application is affected by GHSA-8892-84wf-cg8f, inspect your project dependencies for SyncChannel<T> can move 'T:

inspect dependencies for signal-simple

Analyze the terminal output to locate any version of SyncChannel<T> can move 'T in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), where the product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. In SyncChannel<T> can move 'T, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Affected versions of this crate unconditionally implement Send/Sync for `SyncChannel<T>`. `SyncChannel<T>` 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<T>` allows to unlock a mutex from a thread that didn't lock the mutex.

GHSA-8892-84wf-cg8f Affected SyncChannel<T> can move 'T Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
signal-simple
 crates.io
≤ 0.1.1

References

SyncChannel<T> can move 'T Source Repository REPOSITORY
https://github.com/kitsuneninetails/signal-rust/issues/2
SyncChannel<T> can move 'T Source Repository REPOSITORY
https://github.com/kitsuneninetails/signal-rust
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2020-0126.html

Frequently Asked Questions

What is GHSA-8892-84wf-cg8f?
GHSA-8892-84wf-cg8f is a security vulnerability in SyncChannel<T> can move 'T involving !Send' to other threads under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition').
Which SyncChannel<T> can move 'T versions are affected?
Affected versions include releases prior to current release patches across affected packages: signal-simple.
What version fixes GHSA-8892-84wf-cg8f?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is signal-simple affected?
Yes, signal-simple is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of GHSA-8892-84wf-cg8f?
GHSA-8892-84wf-cg8f has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with GHSA-8892-84wf-cg8f?
GHSA-8892-84wf-cg8f is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.).
How can I check crates.io dependencies for GHSA-8892-84wf-cg8f?
Run the dependency tree command: 'inspect dependencies for signal-simple'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8892-84wf-cg8f",
  "modified" : "2023-06-13T21:01:55Z",
  "published" : "2021-08-25T21:00:16Z",
  "aliases" : [ ],
  "summary" : "SyncChannel<T> can move 'T: !Send' to other threads",
  "details" : "Affected versions of this crate unconditionally implement Send/Sync for `SyncChannel<T>`. `SyncChannel<T>` 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<T>` allows to unlock a mutex from a thread that didn't lock the mutex.\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "signal-simple"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.1.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kitsuneninetails/signal-rust/issues/2"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kitsuneninetails/signal-rust"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2020-0126.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-362" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-06T18:04:55Z",
    "nvd_published_at" : null
  }
}