CVE-2019-19391

Name	CVE-2019-19391
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
Source	CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
Debian Bugs	946053

Vulnerable and fixed packages

The table below lists information on source packages.

Source Package	Release	Version	Status
luajit (PTS)	buster	2.1.0~beta3+dfsg-5.1	vulnerable
	bullseye	2.1.0~beta3+dfsg-5.3	vulnerable
	bookworm	2.1.0~beta3+git20220320+dfsg-4.1	fixed
	sid, trixie	2.1.0+openresty20231117-2	fixed

The information below is based on the following data on fixed versions.

Package	Type	Release	Fixed Version	Urgency	Origin	Debian Bugs
luajit	source	(unstable)	2.1.0~beta3+git20210112+dfsg-2	unimportant		946053

Notes

https://github.com/LuaJIT/LuaJIT/pull/526
Negligible security impact. The debug library is unsafe per se and one is
not supposed to release an application with the debug library.