Local interpreter crash via corrupted call frame
Published Jan 11, 2022 · Updated Aug 4, 2024
Type confusion in Lua 5.4.3 allows local users to crash the interpreter through error handling in a crafted script. During traceback construction, funcnamefromcode treats an overwritten previous call-frame value as a Lua function and dereferences it. The trigger requires a variadic function that calls os.exit and an error from a to-be-closed value's __close handler, terminating the interpreter process.
Summary
What happened
Type confusion in Lua 5.4.3 allows local users to crash the interpreter through error handling in a crafted script. During traceback construction, funcnamefromcode treats an overwritten previous call-frame value as a Lua function and dereferences it. The trigger requires a variadic function that calls os.exit and an error from a to-be-closed value's __close handler, terminating the interpreter process.
The record
- CVE
- CVE-2021-44647
- Published
- Jan 11, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-843, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 11, 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.
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.
Weakness, pattern, technique
Public exploit references
- Lua __close error-handling crash reproducerproof of concept · 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