CVE-2024-7884

Memory leak when calling a canister method via `ic_cdk::call`

Published Sep 5, 2024 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed

Description

When a canister method is called via ic_cdk::call* , a new Future CallFuture is created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called CallFutureState. A bug in the polling implementation of the CallFuture allows multiple references to be held for this internal state and not all references were dropped before the Future is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister's heap and thus causing a memory leak.
Impact Canisters built in Rust with ic_cdk and ic_cdk_timers are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. In the worst case, this could lead to heap memory exhaustion triggered by an attacker. Motoko based canisters are not affected by the bug.
PatchesThe patch has been backported to all minor versions between >= 0.8.0, <= 0.15.0. The patched versions available are 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 and their previous versions have been yanked. WorkaroundsThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of ic_cdk to avoid running out of Wasm heap memory.
Upgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it's only a temporary solution.

Affected Products

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

Internet Computer

ic-cdk

unaffected

Version	Status	Constraints
`0.8.0`	affected	< 0.8.2
`0.9.0`	affected	< 0.9.3
`0.10.0`	affected	< 0.10.1
`0.11.0`	affected	< 0.11.5
`0.12.0`	affected	< 0.12.2
`0.13.0`	affected	< 0.13.4
`0.14.0`	affected	< 0.14.1
`0.15.0`	affected	< 0.15.1

Configuration 1 [-]

OR	cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer::::::rust::*
	cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer::::::rust::*
	cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer::::::rust::*
	cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer::::::rust::*
	cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer::::::rust::*
	cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.10.0:::::rust::
	cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.14.0:::::rust::
	cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.15.0:::::rust::

No data.

No data available yet.

Remediation

No solution or workaround provided in the CVE record

Tracking

Advisories

Source	ID	Title
EUVD	EUVD-2024-2871	When a canister method is called via ic_cdk::call* , a new Future CallFuture is created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called CallFutureState. A bug in the polling implementation of the CallFuture allows multiple references to be held for this internal state and not all references were dropped before the Future is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister's heap and thus causing a memory leak. Impact Canisters built in Rust with ic_cdk and ic_cdk_timers are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. In the worst case, this could lead to heap memory exhaustion triggered by an attacker. Motoko based canisters are not affected by the bug. PatchesThe patch has been backported to all minor versions between >= 0.8.0, <= 0.15.0. The patched versions available are 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 and their previous versions have been yanked. WorkaroundsThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of ic_cdk to avoid running out of Wasm heap memory. Upgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it's only a temporary solution.
Github GHSA	GHSA-rwq6-crjg-9cpw	ic-cdk has a memory leak when calling a canister method via `ic_cdk::call`

Metrics

No CVSS v4.0

Attack Vector Network

Attack Complexity Low

Privileges Required None

Scope Unchanged

Confidentiality Impact None

Integrity Impact None

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploit prediction score: < 1% (0.693% probability within 30 days)

Exploitation none

Automatable yes

Technical Impact partial

References

Link	Providers
https://docs.rs/ic-cdk/latest/ic_cdk/
https://github.com/dfinity/cdk-rs/pull/509
https://internetcomputer.org/docs/current/references/ic-interface-spec

History

Sep 12, 2024 9:15 PM First appearance in the feed. Affected versions updated. Affected vendors updated View changes

Type	Values Removed	Values Added
First Time appeared		Dfinity Dfinity canister Developer Kit For The Internet Computer
CPEs		cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer::::::rust::* cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.10.0:::::rust:: cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.14.0:::::rust:: cpe:2.3:a:dfinity:canister_developer_kit_for_the_internet_computer:0.15.0:::::rust::
Vendors & Products		Dfinity Dfinity canister Developer Kit For The Internet Computer

Sep 5, 2024 3:30 PM First appearance in the feed. Affected versions updated. Affected vendors updated. Scoring metrics updated View changes

Type	Values Removed	Values Added
First Time appeared		Internet Computer Internet Computer ic-cdk
CPEs		cpe:2.3:a:internet_computer:ic-cdk::::::::
Vendors & Products		Internet Computer Internet Computer ic-cdk
Metrics		ssvc `{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}`

Sep 5, 2024 1:15 PM Description updated. Title updated. Weaknesses updated. Added references. Scoring metrics updated View changes

Type	Values Removed	Values Added
Description		When a canister method is called via ic_cdk::call* , a new Future CallFuture is created and can be awaited by the caller to get the execution result. Internally, the state of the Future is tracked and stored in a struct called CallFutureState. A bug in the polling implementation of the CallFuture allows multiple references to be held for this internal state and not all references were dropped before the Future is resolved. Since we have unaccounted references held, a copy of the internal state ended up being persisted in the canister's heap and thus causing a memory leak. Impact Canisters built in Rust with ic_cdk and ic_cdk_timers are affected. If these canisters call a canister method, use timers or heartbeat, they will likely leak a small amount of memory on every such operation. In the worst case, this could lead to heap memory exhaustion triggered by an attacker. Motoko based canisters are not affected by the bug. PatchesThe patch has been backported to all minor versions between >= 0.8.0, <= 0.15.0. The patched versions available are 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1 and their previous versions have been yanked. WorkaroundsThere are no known workarounds at the moment. Developers are recommended to upgrade their canister as soon as possible to the latest available patched version of ic_cdk to avoid running out of Wasm heap memory. Upgrading the canisters (without updating `ic_cdk`) also frees the leaked memory but it's only a temporary solution.
Title		Memory leak when calling a canister method via `ic_cdk::call`
Weaknesses		CWE-401
References		https://docs.rs/ic-cdk/latest/ic_cdk/ https://github.com/dfinity/cdk-rs/pull/509 https://internetcomputer.org/docs/current/references/ic-interface-spec
Metrics		cvssV3_1 `{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}`