Application crash via recursive error handling
Published Jul 1, 2022 · Updated Aug 3, 2024
Heap-buffer overflow in Lua 5.4.2 through 5.4.4 allows remote attackers to crash embedding applications by triggering recursive errors. The luaG_runerror path retains intermediate error values in reserved EXTRA_STACK slots while recurring calls to luaG_errormsg consume additional stack space, eventually overflowing the heap-backed Lua stack buffer. Attacker-controlled Lua code must run in the embedding application and trigger an error during error handling; the demonstrated consequence is an application crash, not code execution.
Summary
What happened
Heap-buffer overflow in Lua 5.4.2 through 5.4.4 allows remote attackers to crash embedding applications by triggering recursive errors. The luaG_runerror path retains intermediate error values in reserved EXTRA_STACK slots while recurring calls to luaG_errormsg consume additional stack space, eventually overflowing the heap-backed Lua stack buffer. Attacker-controlled Lua code must run in the embedding application and trigger an error during error handling; the demonstrated consequence is an application crash, not code execution.
The record
- CVE
- CVE-2022-33099
- Published
- Jul 1, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- Lua recursive-error minimal 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