LuaJIT
Products
1- 6 CVEs
Recent CVEs
6| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2020-24372 | Hig | 0.49 | 7.5 | 0.01 | Aug 17, 2020 | LuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in lj_err.c. | ||
| CVE-2020-15890 | Hig | 0.49 | 7.5 | 0.03 | Jul 21, 2020 | LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled. | ||
| CVE-2024-25178 | Cri | 0.00 | 9.1 | 0.01 | Jul 7, 2025 | 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 | Hig | 0.00 | 7.5 | 0.00 | Jul 7, 2025 | 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 | Cri | 0.00 | 9.8 | 0.00 | Jul 7, 2025 | 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-2019-19391 | Cri | 0.00 | 9.1 | 0.01 | Nov 29, 2019 | 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… |
- risk 0.49cvss 7.5epss 0.01
LuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in lj_err.c.
- risk 0.49cvss 7.5epss 0.03
LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled.
- risk 0.00cvss 9.1epss 0.01
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.
- risk 0.00cvss 7.5epss 0.00
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).
- risk 0.00cvss 9.8epss 0.00
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.
- risk 0.00cvss 9.1epss 0.01
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…