Host-process crash via uncounted recursive closure calls
Published Jun 13, 2024 · Updated Aug 2, 2024
Stack overflow in Rhai 1.18.0 allows remote attackers to crash an embedding application via a recursively invoked closure method. Engine method-call paths invoke call_script_fn without incrementing the global recursion level, bypassing the configured depth limit. An application must evaluate attacker-controlled Rhai code that recursively calls a closure method; native stack exhaustion then terminates the host process.
Summary
What happened
Stack overflow in Rhai 1.18.0 allows remote attackers to crash an embedding application via a recursively invoked closure method. Engine method-call paths invoke call_script_fn without incrementing the global recursion level, bypassing the configured depth limit. An application must evaluate attacker-controlled Rhai code that recursively calls a closure method; native stack exhaustion then terminates the host process.
The record
- CVE
- CVE-2024-36760
- Published
- Jun 13, 2024
- Updated
- Aug 2, 2024
- Vendor
- Rhai
- Product
- Rhai
- Classifications
- CWE-120, CWE-674, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.18.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Recursive closure stack-overflow reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo