Sandbox escape via reentrant garbage collection
Published Mar 14, 2022 · Updated Aug 4, 2024
Use-after-free in Lua 5.4.0 through 5.4.3 allows attackers to escape an embedding application's sandbox via a crafted script. The lgc.c finalizer path permits a __gc metamethod to reenter the non-reentrant collector, leaving freed heap storage reusable and corruptible. The host must execute attacker-controlled Lua code with finalizers enabled; a public Linux exploit poisons tcache to replace __free_hook with system and launch a shell.
Summary
What happened
Use-after-free in Lua 5.4.0 through 5.4.3 allows attackers to escape an embedding application's sandbox via a crafted script. The lgc.c finalizer path permits a __gc metamethod to reenter the non-reentrant collector, leaving freed heap storage reusable and corruptible. The host must execute attacker-controlled Lua code with finalizers enabled; a public Linux exploit poisons tcache to replace __free_hook with system and launch a shell.
The record
- CVE
- CVE-2021-44964
- Published
- Mar 14, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 14, 2022CVE 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.
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
- lua-5.4.4-sandbox-escape exploitfunctional · demonstrated
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