Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

string-interner

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. High, CVSS 7.5crates.ioPublished

    Use after free in string-interner

    CVE-2019-16882 · GHSA-49fq-pw77-6qxj

    Affected
    • crates.io string-interner >= 0.7.0, < 0.7.1; < 0.6.4
    Fixed in
    0.6.40.7.1· Vendor fix available
    Issue
    Affected versions of this crate did not clone contained strings when an interner is cloned. Interners have raw pointers to the contained strings, and they keep pointing the strings which the old interner owns, after the interner is cloned. If a new cloned interner is alive and the old original interner is dead, the new interner has dangling pointers to the old interner's storage, which is already dropped. This allows an attacker to read the already freed memory. The dangling pointers are used by the interners to check a string is already interned. An attacker can do brute force attack to get the data pointed by the dangling pointer.

    Recommended action: Upgrade to 0.7.1 or 0.6.4 by release line, 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 →