Infinite decoding loop through specially crafted payload
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 1.2%
exploitation probability
1.2%top 34% of all CVEs
observed exploitation
nono source reports it
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:H
Affected products
Internet Computer · CandidReferences
https://github.com/dfinity/candid/blob/master/spec/Candid.mdhttps://github.com/dfinity/candid/pull/478https://github.com/dfinity/candid/security/advisories/GHSA-7787-p7x6-fq3jhttps://internetcomputer.org/docs/current/references/candid-refhttps://internetcomputer.org/docs/current/references/ic-interface-spec