Most recent entries from all

cnvd-2021-31472

EUVD-2026-26928

fkie_cve-2021-30455

An issue was discovered in the id-map crate through 2021-02-26 for Rust. A double free can occur in IdMap::clone_from upon a .clone panic.

GHSA-8gmx-cpcg-f8h5 — Double-free in id-map

Affected: crates.io: id-map

The clone_from implementation for IdMap drops the values present in the map and then begins cloning values from the other map. If a .clone() call pancics, then the afformentioned dropped elements can be freed again. get_or_insert

get_or_insert reserves space for a value, before calling the user provided insertion function f. If the function f panics then uninitialized or previously freed memory can be dropped. remove_set

When removing a set of elements, ptr::drop_in_place is called on each of the element to be removed. If the Drop impl of one of these elements panics then the previously dropped elements can be dropped again.

gsd-2021-30455

RUSTSEC-2021-0052 — Multiple functions can cause double-frees

Affected: crates.io: id-map

The following functions in the crate are affected:

## `IdMap::clone_from`

The `clone_from` implementation for `IdMap` drops the values present in the map and then begins cloning values from the other map. If a `.clone()` call pancics, then the afformentioned dropped elements can be freed again.

## `get_or_insert`

`get_or_insert` reserves space for a value, before calling the user provided insertion function `f`. If the function `f` panics then uninitialized or previously freed memory can be dropped.

## `remove_set`

When removing a set of elements, `ptr::drop_in_place` is called on each of the element to be removed. If the `Drop` impl of one of these elements panics then the previously dropped elements can be dropped again.