Memory corruption via stale VM stack pointer
Published Mar 26, 2022 · Updated Aug 2, 2024
Use-after-free in mruby before 3.2 allows local users to corrupt interpreter memory by executing crafted Ruby code. In mrb_vm_exec, calls such as hash, string, and constant lookups can reallocate the VM stack while an assignment still uses the stale regs pointer. Exploitation requires local execution and user interaction in a privileged hosting context, with compromise bounded to that process and its security context.
Summary
What happened
Use-after-free in mruby before 3.2 allows local users to corrupt interpreter memory by executing crafted Ruby code. In mrb_vm_exec, calls such as hash, string, and constant lookups can reallocate the VM stack while an assignment still uses the stale regs pointer. Exploitation requires local execution and user interaction in a privileged hosting context, with compromise bounded to that process and its security context.
The record
- CVE
- CVE-2022-1071
- Published
- Mar 26, 2022
- Updated
- Aug 2, 2024
- Vendor
- mruby
- Product
- mruby
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 26, 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.dev CVE-2022-1071 bounty artifactproof 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