Arbitrary code execution via failed reallocation double-free
Published Jul 1, 2021 · Updated Aug 4, 2024
Double free in mruby 2.1.2 allows context-dependent attackers to corrupt heap memory through a failed memory reallocation. In src/gc.c, mrb_realloc freed the original pointer when mrb_realloc_simple returned NULL, then raised an out-of-memory exception while an object still referenced that allocation. Reachability depends on a host application processing attacker-controlled Ruby input and entering this cleanup path; the resulting corruption can crash the host or enable code execution.
Summary
What happened
Double free in mruby 2.1.2 allows context-dependent attackers to corrupt heap memory through a failed memory reallocation. In src/gc.c, mrb_realloc freed the original pointer when mrb_realloc_simple returned NULL, then raised an out-of-memory exception while an object still referenced that allocation. Reachability depends on a host application processing attacker-controlled Ruby input and entering this cleanup path; the resulting corruption can crash the host or enable code execution.
The record
- CVE
- CVE-2020-36401
- Published
- Jul 1, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1203
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 1, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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