Interpreter crash via unchecked super target class
Published Apr 2, 2022 · Updated Aug 2, 2024
NULL pointer dereference in mrb_vm_exec in mruby before 3.2 allows local users to crash the interpreter through a super call. During super handling after a module target, mrb_vm_ci_target_class can return NULL, but mrb_vm_exec dereferences target_class->tt without checking it. Triggering requires local execution of crafted Ruby code in an interpreter or embedding application and causes only that process to crash.
Summary
What happened
NULL pointer dereference in mrb_vm_exec in mruby before 3.2 allows local users to crash the interpreter through a super call. During super handling after a module target, mrb_vm_ci_target_class can return NULL, but mrb_vm_exec dereferences target_class->tt without checking it. Triggering requires local execution of crafted Ruby code in an interpreter or embedding application and causes only that process to crash.
The record
- CVE
- CVE-2022-1201
- Published
- Apr 2, 2022
- Updated
- Aug 2, 2024
- Vendor
- mruby
- Product
- mruby
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 2, 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
- Huntr CVE-2022-1201 exploit reportproof of concept · unverified
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