Skip to content

← Public intelligence

crates.io package

lru

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

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

  1. Low, CVSS 2.7crates.ioPublished

    IterMut violates Stacked Borrows by invalidating internal pointer

    GHSA-rhfx-m35p-ff5j

    Affected
    • crates.io lru >= 0.9.0, < 0.16.3
    Fixed in
    0.16.3· Vendor fix available
    Issue
    Affected versions of this crate contain a soundness issue in the IterMut iterator implementation. The IterMut::next and IterMut::nextback methods temporarily create an exclusive reference to the key when dereferencing the internal node pointer. This invalidates the shared pointer held by the internal HashMap, violating Stacked Borrows rules.

    Recommended action: Upgrade to 0.16.3 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. Unratedcrates.ioPublished

    Use after free in lru crate

    GHSA-qqmc-hwqp-8g2w

    Affected
    • crates.io lru < 0.7.1
    Fixed in
    0.7.1· Vendor fix available
    Issue
    Lru crate has use after free vulnerability. Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.

    Recommended action: Upgrade to 0.7.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 →
  3. High, CVSS 7.5crates.ioPublished

    Use After Free in lru

    CVE-2021-45720 · GHSA-v362-2895-h9r2

    Affected
    • crates.io lru < 0.7.1
    Fixed in
    0.7.1· Vendor fix available
    Issue
    Lru crate has two functions for getting an iterator. Both iterators give references to key and value. Calling specific functions, like pop(), will remove and free the value, and but it's still possible to access the reference of value which is already dropped causing use after free.

    Recommended action: Upgrade to 0.7.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 →