Lucene search
+L

9 matches found

EUVD
EUVD
•added 2025/10/03 8:07 p.m.•18 views

EUVD-2024-2871

Malicious code in bioql PyPI...

7.5CVSS6.3AI score0.00693EPSS
SaveExploits0References9
Github Security Blog
Github Security Blog
•added 2024/09/05 4:44 p.m.•27 views

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

When a canister method is called via iccdk::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...

7.5CVSS7.7AI score0.00693EPSS
SaveExploits0References8Affected Software1
OSV
OSV
•added 2024/09/05 4:44 p.m.•30 views

GHSA-RWQ6-CRJG-9CPW ic-cdk has a memory leak when calling a canister method via `ic_cdk::call`

When a canister method is called via iccdk::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...

8.7CVSS7.6AI score0.00693EPSS
SaveExploits0References8
NVD
NVD
•added 2024/09/05 1:15 p.m.•19 views

CVE-2024-7884

When a canister method is called via iccdk::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...

7.5CVSS0.00693EPSS
SaveExploits0References3
Cvelist
Cvelist
•added 2024/09/05 1:01 p.m.•38 views

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

When a canister method is called via iccdk::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...

7.5CVSS0.00693EPSS
SaveExploits0References3
Vulnrichment
Vulnrichment
•added 2024/09/05 1:01 p.m.•20 views

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

When a canister method is called via iccdk::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...

7.5CVSS7AI score0.00693EPSS
SaveExploits0References3
CVE
CVE
•added 2024/09/05 1:01 p.m.•60 views

CVE-2024-7884

The CVE-2024-7884 issue affects Rust canisters using ic_cdk and ic_cdk_timers when calling a canister method via ic_cdk::call*: a bug in CallFuture polling allows multiple internal state references to persist, causing a leaked copy of CallFutureState in the Wasm heap and memory growth. This memor...

7.5CVSS7.6AI score0.00693EPSS
SaveExploits0References3Affected Software1
OSV
OSV
•added 2024/09/05 12:00 p.m.•30 views

RUSTSEC-2024-0372 Memory leak when calling a canister method via `ic_cdk::call`

When a canister method is called via iccdk::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...

7.5CVSS7.6AI score0.00693EPSS
SaveExploits0References3
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2024/09/05 12:00 a.m.•2 views

CVE-2024-7884: Missing Release of Memory after Effective Lifetime

When a canister method is called via iccdk::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...

7.5CVSS5.7AI score0.00693EPSS
SaveExploits0References1
Rows per page
Query Builder