Canister heap exhaustion via retained CallFuture references
Published Sep 5, 2024 · Updated Sep 5, 2024
Memory leak in DFINITY ic-cdk allows remote attackers to exhaust a Rust canister's Wasm heap through repeated canister operations. CallFuture polling retains multiple references to CallFutureState and resolves the future without dropping every reference, persisting a state copy in the heap. Reachability requires an affected Rust canister to make inter-canister calls, use timers, or run heartbeat logic; Motoko canisters are unaffected.
Summary
What happened
Memory leak in DFINITY ic-cdk allows remote attackers to exhaust a Rust canister's Wasm heap through repeated canister operations. CallFuture polling retains multiple references to CallFutureState and resolves the future without dropping every reference, persisting a state copy in the heap. Reachability requires an affected Rust canister to make inter-canister calls, use timers, or run heartbeat logic; Motoko canisters are unaffected.
The record
- CVE
- CVE-2024-7884
- Published
- Sep 5, 2024
- Updated
- Sep 5, 2024
- Vendor
- DFINITY
- Product
- ic-cdk
- Classifications
- CWE-401, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 5, 2024CVE publishedPublication date reported by the CVE source.
- Sep 5, 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.10.0 <0.10.1
- Affected versionversion=0.10.0 <0.10.1 changes=[{"at":"0.10.1","status":"unaffected"}]
- Affected versionversion=0.11.0 <0.11.5
- Affected versionversion=0.11.0 <0.11.5 changes=[{"at":"0.11.6","status":"unaffected"}]
- Affected versionversion=0.12.0 <0.12.2
- Affected versionversion=0.12.0 <0.12.2 changes=[{"at":"0.12.2","status":"unaffected"}]
- Affected versionversion=0.13.0 <0.13.4
- Affected versionversion=0.13.0 <0.13.4 changes=[{"at":"0.13.5","status":"unaffected"}]
- Affected versionversion=0.14.0 <0.14.1
- Affected versionversion=0.14.0 <0.14.1 changes=[{"at":"0.14.1","status":"unaffected"}]
- Affected versionversion=0.15.0 <0.15.1
- Affected versionversion=0.15.0 <0.15.1 changes=[{"at":"0.15.1","status":"unaffected"}]
- Affected versionversion=0.8.0 <0.8.2
- Affected versionversion=0.8.0 <0.8.2 changes=[{"at":"0.8.2","status":"unaffected"}]
- Affected versionversion=0.9.0 <0.9.3
- Affected versionversion=0.9.0 <0.9.3 changes=[{"at":"0.9.3","status":"unaffected"}]
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