How severe is GHSA-qq4c-hm99-979m?

No CVSS score has been assigned to GHSA-qq4c-hm99-979m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qq4c-hm99-979m?

GHSA-qq4c-hm99-979m affects the following packages: id-map (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-qq4c-hm99-979m?

Update id-map to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qq4c-hm99-979m is resolved across your whole dependency graph.

How do I detect GHSA-qq4c-hm99-979m in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for id-map, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qq4c-hm99-979m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qq4c-hm99-979m?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qq4c-hm99-979m can be triaged on real exposure rather than presence alone.

Is GHSA-qq4c-hm99-979m actively exploited in the wild?

No public exploit code has been indexed for GHSA-qq4c-hm99-979m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qq4c-hm99-979m published, and has it been updated?

GHSA-qq4c-hm99-979m was published on August 18, 2025 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-qq4c-hm99-979m — id-map

Fix: andrewhickman/id-map@fab6922

GHSA-qq4c-hm99-979m is a security vulnerability in id-map. A fix is available for id-map — see the affected versions and patch details below.

IdMap from_iter may lead to uninitialized memory being freed on drop

Also known asRUSTSEC-2025-0050

Published

Aug 18, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀id-map

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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:

slab
slotmap

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`id-map`	≥ 0.1.6&&< 0.2.2	0.2.2`cargo update -p id-map --precise 0.2.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for id-map, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update id-map to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qq4c-hm99-979m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qq4c-hm99-979m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qq4c-hm99-979m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 iterat

O3 Security · Impact-Aware SCA

Is GHSA-qq4c-hm99-979m in your dependencies?

O3 Security finds GHSA-qq4c-hm99-979m across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works