Memory corruption via premature argument-stack flushing
Published Feb 13, 2022 · Updated Aug 2, 2024
Heap buffer overflow in mruby before 3.2 allows local users to corrupt memory by compiling a call with more than 15 arguments. The compiler's gen_values function flushes its value stack when the argument count exceeds the encoded limit, before it packs the completed oversized list into an array. Reachability requires attacker-controlled Ruby source to enter the compiler, and corruption is confined to the process running that source.
Summary
What happened
Heap buffer overflow in mruby before 3.2 allows local users to corrupt memory by compiling a call with more than 15 arguments. The compiler's gen_values function flushes its value stack when the argument count exceeds the encoded limit, before it packs the completed oversized list into an array. Reachability requires attacker-controlled Ruby source to enter the compiler, and corruption is confined to the process running that source.
The record
- CVE
- CVE-2022-0570
- Published
- Feb 13, 2022
- Updated
- Aug 2, 2024
- Vendor
- mruby
- Product
- mruby
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 13, 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