Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

ic-stable-structures

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.9crates.ioPublished

    ic-stable-structures vulnerable to BTreeMap memory leak when deallocating nodes with overflows

    CVE-2024-4435 · GHSA-3rcq-39xp-7xjp

    Affected
    • crates.io ic-stable-structures >= 0.6.0, < 0.6.4
    Fixed in
    0.6.4· Vendor fix available
    Issue
    Impact When storing unbounded types in a BTreeMap, a node is represented as a linked list of "memory chunks". It was discovered recently that when we deallocate a node, in some cases 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 #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. Patches The problem has been fixed in PR #212 and users are asked to upgrade to version…

    Recommended action: Upgrade to 0.6.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →