In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a type confusion issue that leads to arbitrary memory write or read operations, because certain cases involving valid stack levels and > options are mishandled. NOTE: The LuaJIT project owner states that the debug libary is unsafe by definition and that this is not a vulnerability. When LuaJIT was originally developed, the expectation was that the entire debug library had no security guarantees and thus it made no sense to assign CVEs. However, not all users of later LuaJIT derivatives share this perspective
Metrics
Affected Vendors & Products
References
Link | Providers |
---|---|
https://github.com/LuaJIT/LuaJIT/pull/526 |
History
No history.
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2019-11-29T15:18:49
Updated: 2024-08-05T02:16:46.930Z
Reserved: 2019-11-29T00:00:00
Link: CVE-2019-19391
Vulnrichment
Updated: 2024-08-05T02:16:46.930Z
NVD
Status : Modified
Published: 2019-11-29T16:15:10.577
Modified: 2024-11-21T04:34:42.400
Link: CVE-2019-19391
Redhat
No data.