Memory corruption via reallocated VM stack pointer
Published Mar 27, 2022 · Updated Aug 2, 2024
Use-after-free in mrb_vm_exec in mruby before 3.2 allows local users to corrupt memory through crafted range expressions. The OP_RANGE_INC and OP_RANGE_EXC handlers assign through a registers pointer computed before mrb_range_new recursively reallocates the VM stack, leaving the assignment aimed at freed storage. Triggering the flaw requires execution of attacker-controlled Ruby code and can expose or corrupt process memory or crash the interpreter.
Summary
What happened
Use-after-free in mrb_vm_exec in mruby before 3.2 allows local users to corrupt memory through crafted range expressions. The OP_RANGE_INC and OP_RANGE_EXC handlers assign through a registers pointer computed before mrb_range_new recursively reallocates the VM stack, leaving the assignment aimed at freed storage. Triggering the flaw requires execution of attacker-controlled Ruby code and can expose or corrupt process memory or crash the interpreter.
The record
- CVE
- CVE-2022-1106
- Published
- Mar 27, 2022
- Updated
- Aug 2, 2024
- Vendor
- mruby
- Product
- mruby
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 27, 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?
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.
Public exploit references
- huntr.dev proof-of-concept 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