Skip to content
Noroxi
NVD / CVE Program· CNA Dfinity

CVE-2024-7884: Memory leak when calling a canister method via `ic_cdk::call`

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.69% (FIRST EPSS); higher than 53% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Internet Computer ic-cdk 0.10.1, 0.11.5, 0.11.6.

Low priority for now. Upgrade to Internet Computer ic-cdk 0.10.1, 0.11.5, 0.11.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Sep 5, 2024
Updated
Jun 17, 2026
EPSS
0.6% · 53th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · Dfinity
7.5
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-7884

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for dfinity records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
dfinitycanister developer kit for the internet computer

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • dfinity canister developer kit for the internet computer0.8.0 and later · before 0.8.2
  • dfinity canister developer kit for the internet computer0.9.0 and later · before 0.9.3
  • dfinity canister developer kit for the internet computer0.11.0 and later · before 0.11.6
  • dfinity canister developer kit for the internet computer0.12.0 and later · before 0.12.2
  • dfinity canister developer kit for the internet computer0.13.0 and later · before 0.13.5
  • dfinity canister developer kit for the internet computer0.10.0
  • dfinity canister developer kit for the internet computer0.14.0
  • dfinity canister developer kit for the internet computer0.15.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Dfinity). Independent of NVD's CPE analysis and usually ahead of it.

  • Internet Computer ic-cdk

    • 0.8.0 and later · before 0.8.2affected · semverfixed in 0.8.2
    • 0.9.0 and later · before 0.9.3affected · semverfixed in 0.9.3
    • 0.10.0 and later · before 0.10.1affected · semverfixed in 0.10.1
    • 0.11.0 and later · before 0.11.5affected · semverfixed in 0.11.6
    • 0.12.0 and later · before 0.12.2affected · semverfixed in 0.12.2
    • 0.13.0 and later · before 0.13.4affected · semverfixed in 0.13.5
    • 0.14.0 and later · before 0.14.1affected · semverfixed in 0.14.1
    • 0.15.0 and later · before 0.15.1affected · semverfixed in 0.15.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
crates.ioic_cdkfrom 0.10.0 · before 0.10.10.10.1
crates.ioic_cdkfrom 0.11.0 · before 0.11.60.11.6
crates.ioic_cdkfrom 0.12.0 · before 0.12.20.12.2
crates.ioic_cdkfrom 0.13.0 · before 0.13.50.13.5
crates.ioic_cdkfrom 0.14.0 · before 0.14.10.14.1
crates.ioic_cdkfrom 0.15.0 · before 0.15.10.15.1
crates.ioic_cdkfrom 0.8.0 · before 0.8.20.8.2
crates.ioic_cdkfrom 0.9.0 · before 0.9.30.9.3
crates.ioic-cdkfrom 0.10.0-0 · before 0.10.10.10.1
crates.ioic-cdkfrom 0.11.0-0 · before 0.11.60.11.6
crates.ioic-cdkfrom 0.12.0-0 · before 0.12.20.12.2
crates.ioic-cdkfrom 0.13.0-0 · before 0.13.50.13.5
crates.ioic-cdkfrom 0.14.0-0 · before 0.14.10.14.1
crates.ioic-cdkfrom 0.15.0-0 · before 0.15.10.15.1
crates.ioic-cdkfrom 0.16.0-0 · before 0.16.00.16.0
crates.ioic-cdkfrom 0.8.0 · before 0.8.20.8.2
crates.ioic-cdkfrom 0.9.0-0 · before 0.9.30.9.3

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Internet Computer ic-cdk0.10.1Vendor (CNA)
Internet Computer ic-cdk0.11.5Vendor (CNA)
Internet Computer ic-cdk0.11.6Vendor (CNA)
Internet Computer ic-cdk0.12.2Vendor (CNA)
Internet Computer ic-cdk0.13.4Vendor (CNA)
Internet Computer ic-cdk0.13.5Vendor (CNA)
Internet Computer ic-cdk0.14.1Vendor (CNA)
Internet Computer ic-cdk0.15.1Vendor (CNA)
Internet Computer ic-cdk0.8.2Vendor (CNA)
Internet Computer ic-cdk0.9.3Vendor (CNA)
crates.io:ic_cdk0.10.1Package registry (OSV)
crates.io:ic_cdk0.11.6Package registry (OSV)
crates.io:ic_cdk0.12.2Package registry (OSV)
crates.io:ic_cdk0.13.5Package registry (OSV)
crates.io:ic_cdk0.14.1Package registry (OSV)
crates.io:ic_cdk0.15.1Package registry (OSV)
crates.io:ic_cdk0.8.2Package registry (OSV)
crates.io:ic_cdk0.9.3Package registry (OSV)
crates.io:ic-cdk0.10.1Package registry (OSV)
crates.io:ic-cdk0.11.6Package registry (OSV)
crates.io:ic-cdk0.12.2Package registry (OSV)
crates.io:ic-cdk0.13.5Package registry (OSV)
crates.io:ic-cdk0.14.1Package registry (OSV)
crates.io:ic-cdk0.15.1Package registry (OSV)
crates.io:ic-cdk0.16.0Package registry (OSV)
crates.io:ic-cdk0.8.2Package registry (OSV)
crates.io:ic-cdk0.9.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-401 · Missing Release of Memory after Effective Lifetime

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records