Luajit

luajit

6 CVEs • 1 product

Products (1)

Click to collapse

Toggle

CVEs (6)

CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS
CVE-2024-25178 1Luajit 1Luajit Jun 17, 2026 Jul 7, 2025 N/A· v4 9.1 CRITICAL· v3 N/A· v2 LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.
CVE-2024-25177 1Luajit 1Luajit Jun 17, 2026 Jul 7, 2025 N/A· v4 7.5 HIGH· v3 N/A· v2 LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an unsinking of IR_FSTORE for NULL metatable, which leads to Denial of Service (DoS).
CVE-2024-25176 1Luajit 1Luajit Jun 17, 2026 Jul 7, 2025 N/A· v4 9.8 CRITICAL· v3 N/A· v2 LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240626 have a stack-buffer-overflow in lj_strfmt_wfnum in lj_strfmt_num.c.
CVE-2020-24372 1Luajit 1Luajit Jun 17, 2026 Aug 17, 2020 N/A· v4 7.5 HIGH· v3 5.0 MEDIUM· v2 LuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in lj_err.c.
CVE-2020-15890 3Canonical DebianLuajit 3Debian Linux LuajitUbuntu Linux Jun 17, 2026 Jul 21, 2020 N/A· v4 7.5 HIGH· v3 5.0 MEDIUM· v2 LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled.
CVE-2019-19391 2Luajit Moonjit Project 2Luajit Moonjit Jun 17, 2026 Nov 29, 2019 N/A· v4 9.1 CRITICAL· v3 6.4 MEDIUM· v2 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 l...Show more 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 perspectiveShow less