Skip to content

← Public intelligence

crates.io package

candid

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5crates.ioPublished

    Candid infinite decoding loop through specially crafted payload

    CVE-2023-6245 · GHSA-7787-p7x6-fq3j

    Affected
    • crates.io candid >= 0.9.0, < 0.9.10
    Fixed in
    0.9.10· Vendor fix available
    Issue
    Impact 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 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. For asset canister users, dfx versions = 0.14.4 to <= 0.15.2-beta.0 ships asset canister with an affected version of candid. Unaffected - Rust canisters using candid < 0.9.0 or = 0.9.10 - Rust canister interfaces of type other than…

    Recommended action: Upgrade to 0.9.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →