VDB
Sign up
HIGH7.5

GHSA-49fq-pw77-6qxj

Use after free in string-interner

Details

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.

Are you affected?

Enter the version of the package you're using.

Affected packages

crates.io/string-interner
Introduced in: 0.7.0Fixed in: 0.7.1

Upgrade string-interner to 0.7.1 or newer (ecosystem crates.io).

crates.io/string-interner
Introduced in: 0Fixed in: 0.6.4

Upgrade string-interner to 0.6.4 or newer (ecosystem crates.io).

References