CVE-2024-36760
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA stack overflow vulnerability was found in version 1.18.0 of rhai. The flaw position is: (/ SRC/rhai/SRC/eval/STMT. Rs in rhai: : eval: : STMT: : _ $LT $impl $u20 $rhai.. engine.. Engine$GT$::eval_stmt::h3f1d68ce37fc6e96). Due to the stack overflow is a recursive call/SRC/rhai/SRC/eval/STMT. Rs file eval_stmt_block function.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA stack overflow vulnerability exists in rhai version 1.18.0 in the eval_stmt_block function within /src/rhai/src/eval/STMT.rs. The vulnerability is caused by unbounded recursive calls in the eval_stmt function, which can be triggered to cause a denial of service via stack exhaustion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate rhai dependencySearch project Cargo.toml, Cargo.lock, or package manifests for the rhai crate entryAffected if rhai appears as a direct or transitive dependency
-
Determine installed rhai versionRun 'cargo tree -p rhai' or inspect Cargo.lock for the rhai crate versionAffected if version resolves to 1.18.0
-
Identify script evaluation usageSearch source code for calls to RhaiEngine::eval, RhaiEngine::eval_file, or similar evaluation methods that parse and execute Rhai scriptsAffected if the application evaluates Rhai scripts via eval APIs
-
Check if scripts are user-controlledReview code paths that feed scripts to the eval functions; determine if untrusted or externally-sourced scripts can be providedAffected if untrusted or unbounded scripts can be passed to the Rhai engine's eval functions
Environment is affected if rhai version 1.18.0 is in use and untrusted Rhai scripts can be evaluated through eval_stmt_block, allowing unbounded recursion to trigger stack exhaustion
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate to a patched version of rhai that addresses the recursive call issue, or implement recursion limits/bounds checking in the eval_stmt_block function to prevent unbounded recursion.
Check rhai GitHub releases for version greater than 1.18.0 containing the security fix
- 1. Identify all deployments using rhai version 1.18.0 in your codebase
- 2. Check the rhai GitHub repository for security releases or patches addressing CVE-2024-36760
- 3. If a patched version is available, update the dependency in your project (e.g., cargo update, or update version in Cargo.toml)
- 4. Rebuild and test the application to ensure the stack overflow vulnerability is remediated
- 5. Verify that the eval_stmt_block function no longer causes excessive recursion
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36760 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data