https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 27 Oct 2026 04:37:01 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-57954 EUVD-2026-57954 https://cve.radiocsirt.org/vuln/euvd-2026-57954 https://cve.radiocsirt.org/vuln/fkie_cve-2019-16882 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2019-16882 https://cve.radiocsirt.org/vuln/ghsa-49fq-pw77-6qxj <p><strong>Affected:</strong> crates.io: string-interner</p> <p>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&#39;s storage, which is already dropped.</p> <p>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.</p> <p><strong>Affected:</strong> crates.io: string-interner</p> <p>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&#39;s storage, which is already dropped.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-49fq-pw77-6qxj https://cve.radiocsirt.org/vuln/gsd-2019-16882 gsd-2019-16882 https://cve.radiocsirt.org/vuln/gsd-2019-16882 https://cve.radiocsirt.org/vuln/rustsec-2019-0023 <p><strong>Affected:</strong> crates.io: string-interner</p> <p>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&#39;s storage, which is already dropped.</p> <p>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.</p> <p>The flaw was corrected by &lt;https://github.com/Robbepop/string-interner/pull/10&gt;. This patch implements `Clone` manually to the interner type, so that the internal raw pointers always point the strings owned by the same interner.</p> <p>PR #10 was also backported to the 0.6 release line in &lt;https://github.com/Robbepop/string-interner/pull/14&gt; and was released in 0.6.4.</p> <p><strong>Affected:</strong> crates.io: string-interner</p> <p>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&#39;s storage, which is already dropped.</p> <p>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.</p> <p>The flaw was corrected by &lt;https://github.com/Robbepop/string-interner/pull/10&gt;. This patch implements `Clone` manually to the interner type, so that the internal raw pointers always point the strings owned by the same interner.</p> <p>PR #10 was also backported to the 0.6 release line in &lt;https://github.com/Robbepop/string-interner/pull/14&gt; and was released in 0.6.4.</p> https://cve.radiocsirt.org/vuln/rustsec-2019-0023