Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

circular-buffer

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Unratedcrates.ioPublished

    Panic-safety unsoundness in truncate_back, truncate_front, clear, and extend_from_slice (use-after-free / double-free)

    Affected
    • crates.io circular-buffer >= 0.0.0-0, < 2.0.1
    Fixed in
    2.0.1· Vendor fix available
    Issue
    Several methods in `circular-buffer` drop elements before updating the buffer's start/end metadata. If an element's `Drop` panics during the drop, the metadata update is skipped, so the buffer still treats the already-dropped elements as live. When the buffer is later dropped (or used after the panic is caught), those elements are visited again — a use-after-free / double-free reachable from safe Rust. Impact - CWE-415 (Double Free): the same allocation is freed twice. - CWE-416 (Use-After-Free): a freed allocation is accessed during a repeated `Drop`. Reachable entirely from safe Rust via `catch_unwind` with element types whose `Drop` can panic. Fix Fixed in `circular-buffer` 2.0.1 by adjusting the buffer's start/end metadata before the elements are dropped.

    Recommended action: Upgrade to 2.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.devSource checked Evidence →