Vulnerability in Luajit
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
EPSS: 0.013 (68.1th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 9.1 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.
Affected products
- Luajit
- Moonjit_project Moonjit
- N/a — versions n/a
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve@mitre.org (Patch, Third Party Advisory, x_refsource_MISC, Issue Tracking)
- af854a3a-2127-422b-91ae-364da2661108
Frequently asked questions
- What is CVE-2019-19391?
- CVE-2019-19391 is a critical-severity vulnerability in Luajit, classified under Access of Resource Using Incompatible Type (Type Confusion). CVSS score: 9.1/10. Published 2019-11-29.
- How severe is CVE-2019-19391?
- Critical severity. CVSS v3 base score is 9.1 out of 10.
- Is CVE-2019-19391 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.