Advisory

GHSA-7mcq-f592-pf7v

Also known as: RUSTSEC-2025-0044

Summary

Slice Ring Buffer and Slice Deque contains four unique double-free vulnerabilities triggered through safe APIs

Details

The crate `slice-ring-buffer` was developed as a fork of `slice-deque` to continue maintenance and provide security patches, since the latter has been officially unmaintained (RUSTSEC-2020-0158).

While slice-ring-buffer has addressed some previously reported memory safety issues inherited from its fork origin (RUSTSEC-2021-0047), 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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-07-16 14:18 UTC
Modified
2025-10-28 06:29 UTC

Affected packages and fixes

slice-deque

crates.io · All systems

Affected

  • introduced 0, last affected 0.3.0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

slice-ring-buffer

crates.io · All systems

Affected

  • introduced 0, last affected 0.3.4 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences