Skip to main content
No exploitation reportedFix available

CVE-2019-16882

No exploitation reported by the sources we read.

  • Published2019-09-25
  • Fixed in0.7.1 · 0.6.4
  • WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2019-09-2517:15CVE publishedNVD

Versions per branch

NVD · OSV
String-interner project string-interner
BranchAffectedFixed in
0.7< 0.7.10.7.1
0.7≥ 0.7.0-0, < 0.7.10.7.1
0.7≥ 0.7.0, < 0.7.10.7.1
0.x≥ 0.0.0-0, < 0.6.40.6.4
0.6< 0.6.40.6.4

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update String-interner project string-interner to 0.7.1 · 0.6.4

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2019-09-25
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-49fq-pw77-6qxj

Frequently asked questions

What is CVE-2019-16882?

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.

Is CVE-2019-16882 actively exploited?

Active exploitation of CVE-2019-16882 has not been confirmed. Its EPSS score was 1.5% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-16882?

CVE-2019-16882 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running string-interner? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record