CVE Vulnerabilities

CVE-2024-7884

Missing Release of Memory after Effective Lifetime

Published: Sep 05, 2024 | Modified: Sep 12, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

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 canisters 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 its only a temporary solution.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.

Affected Software

Name Vendor Start Version End Version
Canister_developer_kit_for_the_internet_computer Dfinity 0.8.0 (including) 0.8.2 (excluding)
Canister_developer_kit_for_the_internet_computer Dfinity 0.9.0 (including) 0.9.3 (excluding)
Canister_developer_kit_for_the_internet_computer Dfinity 0.11.0 (including) 0.11.6 (excluding)
Canister_developer_kit_for_the_internet_computer Dfinity 0.12.0 (including) 0.12.2 (excluding)
Canister_developer_kit_for_the_internet_computer Dfinity 0.13.0 (including) 0.13.5 (excluding)
Canister_developer_kit_for_the_internet_computer Dfinity 0.10.0 (including) 0.10.0 (including)
Canister_developer_kit_for_the_internet_computer Dfinity 0.14.0 (including) 0.14.0 (including)
Canister_developer_kit_for_the_internet_computer Dfinity 0.15.0 (including) 0.15.0 (including)

Potential Mitigations

  • Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
  • For example, glibc in Linux provides protection against free of invalid pointers.
  • When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
  • To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References