Filtered by vendor Luajit
Subscriptions
Filtered by product Luajit
Subscriptions
Total
6 CVE
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2024-25178 | 1 Luajit | 1 Luajit | 2025-07-24 | 9.1 Critical |
| 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 | 1 Luajit | 1 Luajit | 2025-07-24 | 7.5 High |
| 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 | 1 Luajit | 1 Luajit | 2025-07-24 | 9.8 Critical |
| 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 | 1 Luajit | 1 Luajit | 2024-11-21 | 7.5 High |
| LuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in lj_err.c. | ||||
| CVE-2020-15890 | 4 Canonical, Debian, Luajit and 1 more | 4 Ubuntu Linux, Debian Linux, Luajit and 1 more | 2024-11-21 | 7.5 High |
| LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled. | ||||
| CVE-2019-19391 | 2 Luajit, Moonjit Project | 2 Luajit, Moonjit | 2024-11-21 | 9.1 Critical |
| 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 | ||||
Page 1 of 1.