GHSA-7mcq-f592-pf7v: Slice deque Slice Ring Buffer And Slice Vulnerability

HIGH
Share
CWE-415
Published
Advisory Summary

GHSA-7mcq-f592-pf7v is a HIGH slice ring buffer and slice vulnerability (CWE-415: Double Free) affecting Slice deque libraries in the crates.io ecosystem. The issue involves slice ring buffer and slice deque contains four unique double-free vulnerabilities triggered through safe apis. Remediation is available in the latest vendor maintenance releases.

GHSA-7mcq-f592-pf7v at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-7mcq-f592-pf7v
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-415: Double Free
Affected Product Slice deque
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-7mcq-f592-pf7v

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

slice-deque fixed: Latest secure release 
Upgrade slice-deque to Latest secure release
slice-ring-buffer fixed: Latest secure release 
Upgrade slice-ring-buffer 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 slice-deque

How to Check if You Are Affected

To determine whether your application is affected by GHSA-7mcq-f592-pf7v, inspect your project dependencies for Slice deque:

inspect dependencies for slice-deque

Analyze the terminal output to locate any version of Slice deque 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-415: Double Free, where the product calls free() twice on the same memory address. In Slice deque, 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

The crate [`slice-ring-buffer`](https://crates.io/crates/slice-ring-buffer) was developed as a fork of [`slice-deque`](https://crates.io/crates/slice-deque) to continue maintenance and provide security patches, since the latter has been officially unmaintained ([RUSTSEC-2020-0158](https://rustsec.org/advisories/RUSTSEC-2020-0158.html)). While `slice-ring-buffer` has addressed some previously reported memory safety issues inherited from its fork origin ([RUSTSEC-2021-0047](https://rustsec.org/advisories/RUSTSEC-2021-0047.html)), it still retains multiple unresolved memory corruption vulnerabilities. Specifically, we have discovered four new memory safety bugs, each resulting in double-free violations that can occur when only safe APIs are invoked. These vulnerabilities correspond to four distinct safe APIs in the crate, each exposing unsound and vulnerable behavior due to incorrect usage of unsafe code internally. Unfortunately, the maintainer doesn't have much availability to resolve these issues so there's no concrete timeline for fixes. Community contributions towards fixing these vulnerabilities would be much appreciated.

GHSA-7mcq-f592-pf7v Affected Slice deque Versions

2 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
slice-deque
 crates.io
≤ 0.3.0
slice-ring-buffer
 crates.io
≤ 0.3.4

References

Slice deque Source Repository REPOSITORY
https://github.com/LiquidityC/slice_ring_buffer/issues/12
Slice deque Source Repository REPOSITORY
https://github.com/gnzlbg/slice_deque
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2025-0044.html

Frequently Asked Questions

What is GHSA-7mcq-f592-pf7v?
GHSA-7mcq-f592-pf7v is a security vulnerability in Slice deque involving Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIs under CWE-415: Double Free.
Which Slice deque versions are affected?
Affected versions include releases prior to current release patches across affected packages: slice-deque, slice-ring-buffer.
What version fixes GHSA-7mcq-f592-pf7v?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is slice-deque affected?
Yes, slice-deque is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
Is slice-ring-buffer affected?
Yes, slice-ring-buffer is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-7mcq-f592-pf7v?
GHSA-7mcq-f592-pf7v is classified under CWE-415: Double Free (The product calls free() twice on the same memory address.).
How can I check crates.io dependencies for GHSA-7mcq-f592-pf7v?
Run the dependency tree command: 'inspect dependencies for slice-deque'. 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-7mcq-f592-pf7v",
  "modified" : "2025-07-16T14:18:46Z",
  "published" : "2025-07-16T14:18:46Z",
  "aliases" : [ ],
  "summary" : "Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIs",
  "details" : "The crate [`slice-ring-buffer`](https://crates.io/crates/slice-ring-buffer) was developed as a fork of [`slice-deque`](https://crates.io/crates/slice-deque) to continue maintenance and provide security patches, since the latter has been officially unmaintained ([RUSTSEC-2020-0158](https://rustsec.org/advisories/RUSTSEC-2020-0158.html)).\n\nWhile `slice-ring-buffer` has addressed some previously reported memory safety issues inherited from its fork origin ([RUSTSEC-2021-0047](https://rustsec.org/advisories/RUSTSEC-2021-0047.html)), it still retains multiple unresolved memory corruption vulnerabilities.\n\nSpecifically, we have discovered four new memory safety bugs, each resulting in double-free violations that can occur when only safe APIs are invoked. These vulnerabilities correspond to four distinct safe APIs in the crate, each exposing unsound and vulnerable behavior due to incorrect usage of unsafe code internally.\n\nUnfortunately, the maintainer doesn't have much availability to resolve these issues so there's no concrete timeline for fixes. Community contributions towards fixing these vulnerabilities would be much appreciated.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "slice-deque"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.3.0"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "slice-ring-buffer"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.3.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/LiquidityC/slice_ring_buffer/issues/12"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/gnzlbg/slice_deque"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2025-0044.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-415" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-07-16T14:18:46Z",
    "nvd_published_at" : null
  }
}