CVE-2019-19391 Memory corruption in n/a
Type confusion in LuaJIT debug.getinfo allows arbitrary memory read or write, potentially leading to code execution or data disclosure.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2019-19391?
CVE-2019-19391 is a critical memory corruption vulnerability in n/a, published on 29 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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
Weakness: CWE-843
Which versions are affected by CVE-2019-19391?
It affects 2 products.
Linux distribution packages (1)
luajit openSUSE:Tumbleweed | All versions | 2.1.20250826-1.1 |
Products include Luajit Luajit, Moonjit Project Moonjit.
How do I fix CVE-2019-19391?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2019-19391 being exploited?
There is no known exploitation of CVE-2019-19391 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as AZL-41306, DEBIAN-CVE-2019-19391, GHSA-756f-h55r-pvqq, openSUSE-SU-2024:13922-1, openSUSE-SU-2025:15672-1.