CVE-2019-19391

CRITICAL

LuaJIT <2.0.5 - Memory Corruption

Title source: llm
STIX 2.1

Description

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

References (2)

Core 2
Core References
Issue Tracking, Patch, Third Party Advisory x_refsource_misc
https://github.com/LuaJIT/LuaJIT/pull/526

Scores

CVSS v3 9.1
EPSS 0.0021
EPSS Percentile 43.2%
Attack Vector NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CISA SSVC

Vulnrichment
Exploitation none
Automatable no
Technical Impact partial

Details

CWE
CWE-843
Status published
Products (2)
luajit/luajit < 2.0.5
moonjit_project/moonjit < 2.1.2
Published Nov 29, 2019
Tracked Since Feb 18, 2026