Interpreter crash via unpacked Fiber resume arguments
Published Mar 10, 2022 · Updated Aug 2, 2024
NULL pointer dereference in mruby before 3.2 allows local users to crash the interpreter by running a crafted Ruby program. The fiber_switch path stores 15 or more resume arguments directly in the VM frame even though the call-info format requires that count to be represented as one packed array. Attacker-controlled code must be executed locally or by a consuming application with mruby-fiber included; the documented impact is a process crash without confidentiality or integrity loss.
Summary
What happened
NULL pointer dereference in mruby before 3.2 allows local users to crash the interpreter by running a crafted Ruby program. The fiber_switch path stores 15 or more resume arguments directly in the VM frame even though the call-info format requires that count to be represented as one packed array. Attacker-controlled code must be executed locally or by a consuming application with mruby-fiber included; the documented impact is a process crash without confidentiality or integrity loss.
The record
- CVE
- CVE-2022-0890
- Published
- Mar 10, 2022
- Updated
- Aug 2, 2024
- Vendor
- mruby
- Product
- mruby
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 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
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