What is CVE-2024-7884?

CVE-2024-7884 is a high-severity security vulnerability in ic_cdk (rust), affecting versions >= 0.8.0, < 0.8.2. It is fixed in 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1.

How severe is CVE-2024-7884?

CVE-2024-7884 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of ic_cdk are affected by CVE-2024-7884?

ic_cdk (rust) versions >= 0.8.0, < 0.8.2 is affected.

Is there a fix for CVE-2024-7884?

Yes. CVE-2024-7884 is fixed in 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1. Upgrade to this version or later.

Is CVE-2024-7884 exploitable, and should I be worried?

Whether CVE-2024-7884 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-7884 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-7884?

Upgrade: ic_cdk to 0.8.2 or later, ic_cdk to 0.9.3 or later, ic_cdk to 0.10.1 or later, ic_cdk to 0.11.6 or later, ic_cdk to 0.12.2 or later, ic_cdk to 0.13.5 or later, ic_cdk to 0.14.1 or later, ic_cdk to 0.15.1 or later.

CVE-2024-7884 in ic_cdk

Q: How severe is CVE-2024-7884?

CVE-2024-7884 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of ic_cdk are affected by CVE-2024-7884?

ic_cdk (rust) versions >= 0.8.0, < 0.8.2 is affected.

Q: Is there a fix for CVE-2024-7884?

Yes. CVE-2024-7884 is fixed in 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1. Upgrade to this version or later.

Q: Is CVE-2024-7884 exploitable, and should I be worried?

Whether CVE-2024-7884 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-7884 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-7884?

Upgrade: ic_cdk to 0.8.2 or later, ic_cdk to 0.9.3 or later, ic_cdk to 0.10.1 or later, ic_cdk to 0.11.6 or later, ic_cdk to 0.12.2 or later, ic_cdk to 0.13.5 or later, ic_cdk to 0.14.1 or later, ic_cdk to 0.15.1 or later.

Summary

ic-cdk has a memory leak when calling a canister method via ic_cdk::call

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.

Workarounds

There 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.

[!NOTE]
Upgrading the canisters (without updating ic_cdk) also frees the leaked memory but it's only a temporary solution.

References

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.

CVE-2024-7884 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1); upgrading removes the vulnerable code path.

Affected versions

ic_cdk (>= 0.8.0, < 0.8.2) ic_cdk (>= 0.9.0, < 0.9.3) ic_cdk (>= 0.10.0, < 0.10.1) ic_cdk (>= 0.11.0, < 0.11.5) ic_cdk (>= 0.12.0, < 0.12.2) ic_cdk (>= 0.13.0, < 0.13.4) ic_cdk (>= 0.14.0, < 0.14.1) ic_cdk (>= 0.15.0, < 0.15.1)

Security releases

ic_cdk → 0.8.2 (rust) ic_cdk → 0.9.3 (rust) ic_cdk → 0.10.1 (rust) ic_cdk → 0.11.6 (rust) ic_cdk → 0.12.2 (rust) ic_cdk → 0.13.5 (rust) ic_cdk → 0.14.1 (rust) ic_cdk → 0.15.1 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The 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.

Frequently Asked Questions

What is CVE-2024-7884? CVE-2024-7884 is a high-severity security vulnerability in ic_cdk (rust), affecting versions >= 0.8.0, < 0.8.2. It is fixed in 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1.
How severe is CVE-2024-7884? CVE-2024-7884 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of ic_cdk are affected by CVE-2024-7884? ic_cdk (rust) versions >= 0.8.0, < 0.8.2 is affected.
Is there a fix for CVE-2024-7884? Yes. CVE-2024-7884 is fixed in 0.8.2, 0.9.3, 0.10.1, 0.11.6, 0.12.2, 0.13.5, 0.14.1, 0.15.1. Upgrade to this version or later.
Is CVE-2024-7884 exploitable, and should I be worried? Whether CVE-2024-7884 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-7884 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-7884?
- Upgrade ic_cdk to 0.8.2 or later
- Upgrade ic_cdk to 0.9.3 or later
- Upgrade ic_cdk to 0.10.1 or later
- Upgrade ic_cdk to 0.11.6 or later
- Upgrade ic_cdk to 0.12.2 or later
- Upgrade ic_cdk to 0.13.5 or later
- Upgrade ic_cdk to 0.14.1 or later
- Upgrade ic_cdk to 0.15.1 or later