GHSA-9c9f-7x9p-4wqp: Qcell A Malicious Coder Can Get Vulnerability

HIGH
Published
Advisory Summary

GHSA-9c9f-7x9p-4wqp is a HIGH a malicious coder can get vulnerability (General Security Weakness) affecting Qcell libraries in the crates.io ecosystem. The issue involves a malicious coder can get unsound access to tcell or tlcell memory. Remediation is available by upgrading affected packages to version 0.4.3.

GHSA-9c9f-7x9p-4wqp at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-9c9f-7x9p-4wqp
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Qcell
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-9c9f-7x9p-4wqp

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

qcell fixed: 0.4.3
Upgrade qcell to 0.4.3
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 qcell

How to Check if You Are Affected

To determine whether your application is affected by GHSA-9c9f-7x9p-4wqp, inspect your project dependencies for Qcell:

inspect dependencies for qcell

Analyze the terminal output to locate any version of Qcell in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.4.3), 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 General Security Weakness. In Qcell, 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

This is impossible to do by accident, but by carefully constructing marker types to be covariant, a malicious coder can cheat the singleton check in `TCellOwner` and `TLCellOwner`, giving unsound access to cell memory. This could take the form of getting two mutable references to the same memory, or a mutable reference and an immutable reference. The fix is for the crate to internally force the marker type to be invariant. This blocks the conversion between covariant types which Rust normally allows.

GHSA-9c9f-7x9p-4wqp Affected Qcell Versions

1 component(s)
Fixed Versions:
0.4.3
Product / Package Ecosystem Affected Versions Fixed Version
qcell
crates.io
< 0.4.3
0.4.3

References

Frequently Asked Questions

What is GHSA-9c9f-7x9p-4wqp?
GHSA-9c9f-7x9p-4wqp is a security vulnerability in Qcell involving A malicious coder can get unsound access to TCell or TLCell memory under General Security Weakness.
Which Qcell versions are affected?
Affected versions include releases prior to 0.4.3 across affected packages: qcell.
What version fixes GHSA-9c9f-7x9p-4wqp?
Upgrading to 0.4.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is qcell affected?
Yes, qcell is affected in releases prior to 0.4.3. Upgrade your dependency to 0.4.3 or later.
What CWE is associated with GHSA-9c9f-7x9p-4wqp?
GHSA-9c9f-7x9p-4wqp is classified under General Security Weakness.
How can I check crates.io dependencies for GHSA-9c9f-7x9p-4wqp?
Run the dependency tree command: 'inspect dependencies for qcell'. 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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9c9f-7x9p-4wqp",
  "modified" : "2022-06-17T00:16:11Z",
  "published" : "2022-06-17T00:16:11Z",
  "aliases" : [ ],
  "summary" : "A malicious coder can get unsound access to TCell or TLCell memory",
  "details" : "This is impossible to do by accident, but by carefully constructing\nmarker types to be covariant, a malicious coder can cheat the\nsingleton check in `TCellOwner` and `TLCellOwner`, giving unsound\naccess to cell memory.  This could take the form of getting two\nmutable references to the same memory, or a mutable reference and an\nimmutable reference.\n\nThe fix is for the crate to internally force the marker type to be\ninvariant.  This blocks the conversion between covariant types which\nRust normally allows.\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "qcell"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.4.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/uazu/qcell/issues/20"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/uazu/qcell"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2022-0007.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-06-17T00:16:11Z",
    "nvd_published_at" : null
  }
}