The Candid library causes a Denial of Service while parsing a specially crafted payload with 'empty' data type. For example, if the payload is `record { * ; empty }` and the canister interface expects `record { * }` then the Rust candid decoder treats empty as an extra field required by the type. The problem with the type empty is that the candid Rust library wrongly categorizes empty as a recoverable error when skipping the field and thus causing an infinite decoding loop. Canisters using affected versions of candid are exposed to denial of service by causing the decoding to run indefinitely until the canister traps due to reaching maximum instruction limit per execution round. Repeated exposure to the payload will result in degraded performance of the canister. Note: Canisters written in Motoko are unaffected.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HDfinity Candid
APPDfinity0.9.0 – 0.9.10 (bez)
Related vulnerabilities
Słabe generowanie kluczy ed25519 w bibliotece Dfinity ICP-JS-Core
When a canister method is called via ic_cdk::call* , a new Future CallFuture is created and can be awaited by...
Motoko's incremental garbage collector is impacted by an uninitialized memory access bug, caused by incorrect ...
When storing unbounded types in a BTreeMap, a node is represented as a linked list of "memory chunks". It was ...