Compiler crash via invalid hash-update bytecode
Published Jan 21, 2022 · Updated Aug 2, 2024
NULL pointer dereference in mruby before 3.2 allows local users to crash the compiler by processing crafted Ruby code. The gen_hash code generator emits OP_HASHADD and adjusts the virtual stack even when a hash expression's value is discarded, leaving invalid bytecode state that reaches a null pointer. Execution of attacker-supplied Ruby source is required, and the demonstrated consequence is termination of the compiling or interpreting process rather than data disclosure or modification.
Summary
What happened
NULL pointer dereference in mruby before 3.2 allows local users to crash the compiler by processing crafted Ruby code. The gen_hash code generator emits OP_HASHADD and adjusts the virtual stack even when a hash expression's value is discarded, leaving invalid bytecode state that reaches a null pointer. Execution of attacker-supplied Ruby source is required, and the demonstrated consequence is termination of the compiling or interpreting process rather than data disclosure or modification.
The record
- CVE
- CVE-2022-0326
- Published
- Jan 21, 2022
- Updated
- Aug 2, 2024
- Vendor
- mruby
- Product
- mruby
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2022CVE 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=unspecified <3.2
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.
Public exploit references
No public exploit references are available in this record.
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