Process crash via unchecked null class pointer
Published Jan 17, 2022 · Updated Aug 2, 2024
NULL pointer dereference in mruby before 3.2 allows local users to crash an interpreter or embedding application via crafted Ruby code. The mrb_singleton_class_ptr function passes an object with a null class pointer to prepare_singleton_class, which dereferences obj->c without checking it. Exploitation requires execution of attacker-controlled Ruby code in the affected runtime and interrupts only that hosting process.
Summary
What happened
NULL pointer dereference in mruby before 3.2 allows local users to crash an interpreter or embedding application via crafted Ruby code. The mrb_singleton_class_ptr function passes an object with a null class pointer to prepare_singleton_class, which dereferences obj->c without checking it. Exploitation requires execution of attacker-controlled Ruby code in the affected runtime and interrupts only that hosting process.
The record
- CVE
- CVE-2022-0240
- Published
- Jan 17, 2022
- Updated
- Aug 2, 2024
- Vendor
- mruby
- Product
- mruby
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 17, 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.
Weakness, pattern, technique
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