Skip to content

← Public intelligence

crates.io package

internment

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. Critical, CVSS 9.8crates.ioPublished

    Data race in internment

    CVE-2021-28037 · GHSA-gppw-3h6h-v6q2

    Affected
    • crates.io internment < 0.4.2
    Fixed in
    0.4.2· Vendor fix available
    Issue
    An issue was discovered in the internment crate before 0.4.2 for Rust. There is a data race that can cause memory corruption because of the unconditional implementation of Sync for Intern<T.

    Recommended action: Upgrade to 0.4.2 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 8.1crates.ioPublished

    Use after free in internment

    CVE-2020-35874 · GHSA-96w3-p368-4h8c

    Affected
    • crates.io internment >= 0.3.12, < 0.4.0
    Fixed in
    0.4.0· Vendor fix available
    Issue
    ArcIntern::drop has a race condition where it can release memory which is about to get another user. The new user will get a reference to freed memory. This was fixed by serializing access to an interned object while it is being deallocated. Versions prior to 0.3.12 used stronger locking which avoided the problem.

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