n 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
| Link | Resource |
|---|---|
| https://github.com/LuaJIT/LuaJIT/pull/526 | Issue Tracking Patch Third Party Advisory |
| https://github.com/LuaJIT/LuaJIT/pull/526 | Issue Tracking Patch Third Party Advisory |
| https://lists.debian.org/debian-lts-announce/2025/08/msg00022.html |
Configuration 1 (hide)
|
03 Nov 2025, 19:15
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
21 Nov 2024, 04:34
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/LuaJIT/LuaJIT/pull/526 - Issue Tracking, Patch, Third Party Advisory |
Published : 2019-11-29 16:15
Updated : 2025-11-03 19:15
NVD link : CVE-2019-19391
Mitre link : CVE-2019-19391
CVE.ORG link : CVE-2019-19391
JSON object : View
Access of Resource Using Incompatible Type ('Type Confusion')