CVE-2019-16882: Use after free in string-interner
(updated )
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.
References
- github.com/Robbepop/string-interner
- github.com/Robbepop/string-interner/commit/d91dac0cfe42512526879cdfaac0b81beff54089
- github.com/Robbepop/string-interner/issues/9
- github.com/Robbepop/string-interner/pull/10
- github.com/advisories/GHSA-49fq-pw77-6qxj
- nvd.nist.gov/vuln/detail/CVE-2019-16882
- rustsec.org/advisories/RUSTSEC-2019-0023.html
Detect and mitigate CVE-2019-16882 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →