Advisory

RUSTSEC-2025-0050

Also known as: GHSA-qq4c-hm99-979m

Summary

IdMap::from_iter may lead to uninitialized memory being freed on drop

Details

Due to a flaw in the constructor id_map::IdMap::from_iter, ill-formed objects may be created in which the amount of actually initialized memory is less than what is expected by the fields of IdMap. Specifically, the field ids is initialized based on the capacity of the vector values, which is constructed from the provided iterator. However, the length of this vector may be smaller than its capacity.

In such cases, when the resulting IdMap is dropped, its destructor incorrectly assumes that values contains ids.len() == values.capacity() initialized elements and attempts to iterate over and drop them. This leads to dereferencing and attempting to free uninitialized memory, resulting in undefined behavior and potential segmentation faults.

The bug was fixed in commit fab6922, and all unsafe code was removed from the crate.

Note that the maintainer recommends using the following alternatives:

Severity

Not rated by the source.

Dates

Published
2025-08-14 12:00 UTC
Modified
2025-10-28 06:29 UTC

Affected packages and fixes

id-map

crates.io · All systems

Affected

  • introduced 0.1.6, fixed 0.2.2 (semver)

Fixed versions

0.2.2

Fix

  • Fixed version 0.2.2
    cargo update -p id-map --precise 0.2.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences