Local runtime crash via uninitialized register count
Published Jul 9, 2025 · Updated Jul 9, 2025
Heap-based buffer overflow in mruby 3.4.0-rc1 and 3.4.0-rc2 allows local users to crash the runtime with crafted Ruby source. scope_new initializes nlocals from the scope stack pointer but leaves nregs unset, allowing VM stack_clear to write past the allocated stack. A local user or embedding application must cause the compiler to process the crafted source; demonstrated impact is an AddressSanitizer-detected abort.
Summary
What happened
Heap-based buffer overflow in mruby 3.4.0-rc1 and 3.4.0-rc2 allows local users to crash the runtime with crafted Ruby source. scope_new initializes nlocals from the scope stack pointer but leaves nregs unset, allowing VM stack_clear to write past the allocated stack. A local user or embedding application must cause the compiler to process the crafted source; demonstrated impact is an AddressSanitizer-detected abort.
The record
- CVE
- CVE-2025-7207
- Published
- Jul 9, 2025
- Updated
- Jul 9, 2025
- Vendor
- mruby
- Product
- mruby
- Classifications
- CWE-787, CWE-122, CWE-119, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2025CVE publishedPublication date reported by the CVE source.
- Jul 9, 2025Record 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=3.4.0-rc1
- Affected versionversion=3.4.0-rc2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- mruby_crash.txt proof-of-concept inputproof 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