# CVE-2024-4435: BTreeMap memory leak when deallocating nodes with overflows > Attackers can trigger a memory leak in BTreeMap by storing unbounded types, leading to excessive memory consumption and potential denial of service. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 May 2024 - **Updated:** 1 Aug 2024 - **Also known as:** GHSA-3rcq-39xp-7xjp, RUSTSEC-2024-0406 ## What is CVE-2024-4435? CVE-2024-4435 is a medium-severity denial of service vulnerability in Internet Computer ic-stable-structures, published on 21 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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 https://github.com/dfinity/stable-structures/pull/212  by changing the logic for deallocating nodes to ensure that all of a node's memory chunks are deallocated and users are asked to upgrade to version 0.6.4.. Tests have been added to prevent regressions of this nature moving forward. Note: Users of stable-structure < 0.6.0 are not affected. 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. Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime) ## Which versions are affected by CVE-2024-4435? 3 open source packages ship an affected version, including ic-stable-structures. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ic-stable-structures` | crates.io | From 0.6.0 | 0.6.4 | | `ic-stable-structures` | crates.io | From 0.6.0 | 0.6.4 | | `ic-stable-structures` | crates.io | From 0.6.0 | 0.6.4 | Products: Dfinity Stable Structures. ## How do I fix CVE-2024-4435? Upgrade ic-stable-structures to 0.6.4 or later. ## Is CVE-2024-4435 being exploited? There is no known exploitation of CVE-2024-4435 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-4435 and fix it if it is affected. What it is: CVE-2024-4435 is a medium-severity denial of service vulnerability in Internet Computer ic-stable-structures, published on 21 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-4435 in the wild and no public exploit code. Affected packages and fixed versions: - ic-stable-structures (crates.io): affected from 0.6.0; fixed in 0.6.4 - ic-stable-structures (crates.io): affected from 0.6.0; fixed in 0.6.4 - ic-stable-structures (crates.io): affected from 0.6.0; fixed in 0.6.4 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-4435/ (Markdown: https://insights.sbomify.com/CVE-2024-4435/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4435 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4435 - OSV: https://osv.dev/vulnerability/CVE-2024-4435 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-4435/ Summaries are generated and may contain mistakes; the official description above is the record.