CVE-2024-4435 json
BTreeMap memory leak when deallocating nodes with overflows
published 2024-05-17 2 y ago modified 2026-06-17 4 mo ago also GHSA-3rcq-39xp-7xjp , RUSTSEC-2024-0406 , EUVD-2024-1394
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io ic-stable-structures 0.6.4
- Internet Computer ic-stable-structures 0.6.4
- github.com/dfinity/stable-structures@4f6b8ae commit
- github.com/dfinity/stable-structures#212 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ic-stable-structures | >=0.6.0, <0.6.4 |
0.6.4 |
Affected products
- Internet Computer ic-stable-structures
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
References
-
github.com
/dfinity/stable-structures/pull/212
web, issue-tracking, patch
-
github.com
/dfinity/stable-structures/commit/4f6b8ae521884833498bae26369c353c10f28ea7
web
-
docs.rs
/ic-stable-structures/0.6.4/ic_stable_structures/
product
-
internetcomputer.org
/docs/current/developer-docs/smart-contracts/maintain/storage#stable-memory
web, product
-
github.com
/dfinity/stable-structures/security/advisories/GHSA-3rcq-39xp-7xjp
web
-
nvd.nist.gov
/vuln/detail/CVE-2024-4435
advisory
-
docs.rs
/ic-stable-structures/0.6.4/ic_stable_structures
web
-
github.com
/dfinity/stable-structures
package
-
rustsec.org
/advisories/RUSTSEC-2024-0406.html
web, advisory
-
crates.io
/crates/ic-stable-structures
package
Sources
- CVE List CVE-2024-4435
- GitHub Advisory GHSA-3rcq-39xp-7xjp
- NVD CVE-2024-4435
- OSV RUSTSEC-2024-0406
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.