Advisory

RUSTSEC-2024-0406

Also known as: CVE-2024-4435, GHSA-3rcq-39xp-7xjp

Summary

BTreeMap memory leak when deallocating nodes with overflows

Details

When storing unbounded types in a BTreeMap, a node is represented as a linked list of "memory chunks". In some cases, when we deallocate a node only the first memory chunk is deallocated, and the rest of the memory chunks remain (incorrectly) allocated, causing a memory leak.

In the worst case, depending on how a canister uses the BTreeMap, an adversary could interact with the canister through its API and trigger interactions with the map that keep consuming memory due to the memory leak. This could potentially lead to using an excessive amount of memory, or even running out of memory.

This issue has been fixed in dfinity/stable-structures/pull/212 by changing the logic for deallocating nodes to ensure that all of a node's memory chunks are deallocated. Tests have been added to prevent regressions of this nature moving forward.

Note: Users of stable-structure < 0.6.0 are not affected.

Workarounds
Users who are not storing unbounded types in BTreeMap are not affected and do not need to upgrade. Otherwise, an upgrade to version 0.6.4 is necessary.

References

Severity

Medium Basis: CVSS v3 score 5.9, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Dates

Published
2024-05-17 12:00 UTC
Modified
2024-12-04 12:58 UTC

Affected packages and fixes

ic-stable-structures

crates.io · All systems

Affected

  • introduced 0.6.0, fixed 0.6.4 (semver)

Fixed versions

0.6.4

Fix

  • Fixed version 0.6.4
    cargo update -p ic-stable-structures --precise 0.6.4

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