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
History

Mon, 03 Nov 2025 19:30:00 +0000

Type Values Removed Values Added
References

Mon, 03 Nov 2025 19:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published: 2019-11-29T15:18:49.000Z

Updated: 2025-11-03T18:07:53.427Z

Reserved: 2019-11-29T00:00:00.000Z

Link: CVE-2019-19391

cve-icon Vulnrichment

Updated: 2025-11-03T18:07:53.427Z

cve-icon NVD

Status : Modified

Published: 2019-11-29T16:15:10.577

Modified: 2025-11-03T19:15:39.210

Link: CVE-2019-19391

cve-icon Redhat

No data.