Service interruption via incomplete memory-chunk deallocation
Published May 21, 2024 · Updated Aug 1, 2024
Memory leak in DFINITY Foundation ic-stable-structures 0.6.0 through 0.6.3 allows remote attackers to exhaust canister memory. The BTreeMap node-deallocation path releases only the first chunk in a linked overflow chain, leaving the remaining chunks allocated. Reachability requires a canister API that permits repeated mutation of a BTreeMap storing unbounded types; accumulated stable-memory loss can interrupt that canister.
Summary
What happened
Memory leak in DFINITY Foundation ic-stable-structures 0.6.0 through 0.6.3 allows remote attackers to exhaust canister memory. The BTreeMap node-deallocation path releases only the first chunk in a linked overflow chain, leaving the remaining chunks allocated. Reachability requires a canister API that permits repeated mutation of a BTreeMap storing unbounded types; accumulated stable-memory loss can interrupt that canister.
The record
- CVE
- CVE-2024-4435
- Published
- May 21, 2024
- Updated
- Aug 1, 2024
- Vendor
- DFINITY Foundation
- Product
- ic-stable-structures
- Classifications
- CWE-401, CAPEC-131, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.6.0 <0.6.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo