Skip to content

← Public intelligence

crates.io package

bumpalo

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

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

  1. Unratedcrates.ioPublished

    bumpalo has use-after-free due to a lifetime error in Vec::into_iter()

    GHSA-f85w-wvc7-crwc

    Affected
    • crates.io bumpalo >= 1.1.0, < 3.11.1
    Fixed in
    3.11.1· Vendor fix available
    Issue
    In affected versions of this crate, the lifetime of the iterator produced by Vec::intoiter() is not constrained to the lifetime of the Bump that allocated the vector's memory. Using the iterator after the Bump is dropped causes use-after-free accesses. The following example demonstrates memory corruption arising from a misuse of this unsoundness. The issue was corrected in version 3.11.1 by adding a lifetime to the IntoIter type, and updating the signature of Vec::intoiter() to constrain this lifetime.

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

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5crates.ioPublished

    Out of bounds read in bumpalo

    CVE-2020-35861 · GHSA-vqx7-pw4r-29rr

    Affected
    • crates.io bumpalo >= 3.0.0, < 3.2.1
    Fixed in
    3.2.1· Vendor fix available
    Issue
    An issue was discovered in the bumpalo crate before 3.2.1 for Rust. The realloc feature allows the reading of unknown memory. Attackers can potentially read cryptographic keys.

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

    Sources:github.comSource checked Evidence →