Most recent entries from all

Withdrawn: BELL-CVE-2019-19391 — CVE-2019-19391 does not affect BellSoft software

Withdrawn by the publisher.

cnvd-2019-46265

EUVD-2026-257494

fkie_cve-2019-19391

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

GHSA-756f-h55r-pvqq

gsd-2019-19391

msrc_CVE-2019-19391 — In LuaJIT through 2.0.5 as used in Moonjit before 2.1.2 and other products debug.getinfo has a type confusion issue tha…

msrc_CVE-2019-19391

openSUSE-SU-2024:13922-1 — libluajit2-5_1-2-2.1.20240314-1.1 on GA media

libluajit2-5_1-2-2.1.20240314-1.1 on GA media

Withdrawn: UBUNTU-CVE-2019-19391

Withdrawn by the publisher.

Affected: Ubuntu:24.04:LTS: luajit

** DISPUTED ** 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.