Interpreter crash via undersized vararg stack reservation
Published Sep 4, 2014 · Updated Aug 6, 2024
Buffer overflow in Lua 5.1 through 5.2.2 allows context-dependent attackers to crash the interpreter via a crafted vararg call. In ldo.c, luaD_precall reserves only p->maxstacksize slots before padding missing fixed parameters, so the nil writes exceed the Lua stack. An attacker must be able to make a host execute Lua code that defines a vararg function with many fixed parameters and calls it with few arguments.
Summary
What happened
Buffer overflow in Lua 5.1 through 5.2.2 allows context-dependent attackers to crash the interpreter via a crafted vararg call. In ldo.c, luaD_precall reserves only p->maxstacksize slots before padding missing fixed parameters, so the nil writes exceed the Lua stack. An attacker must be able to make a host execute Lua code that defines a vararg function with many fixed parameters and calls it with few arguments.
The record
- CVE
- CVE-2014-5461
- Published
- Sep 4, 2014
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2014CVE publishedPublication date reported by the CVE source.
- Aug 6, 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.
Weakness, pattern, technique
Public exploit references
- Lua upstream vararg 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