cve.bz

CVE-2023-6245 dfinity candid: Infinite Loop

7.5 highEPSS 1.2%Fix available

High (7.5) in dfinity candid. EPSS 1.2% estimated probability of exploitation activity in the next 30 days. Fixed in candid 0.9.10.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
1.2% (unchanged from 1.2% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 69th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2024-12-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
CWE-20 Improper Input Validation
CWE-168 Improper Handling of Inconsistent Special Elements
CWE-1288 Improper Validation of Consistency within Input
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-6245 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-6245?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-6245?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-6245 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Internet Computer Candidfrom 0.9.0 before 0.9.10

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7787-p7x6-fq3jcrates.iocandid>=0.9.0 <0.9.100.9.10
RUSTSEC-2023-0073crates.iocandid>=0.9.0 <0.9.100.9.10

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON