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

Severity
CRITICAL
CVSS v3
9.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N · source nvd
Exploit chance (EPSS)
1.384%
chance of exploitation in the next 30 days
higher than 72.7% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationnone
Automatableno
Technical impactpartial
Scored2024-06-11

Timeline

  1. 2019-11-29Published by the CNA15:18 UTC
  2. 2024-06-11CISA SSVC decision recorded1656 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
luajit luajitthrough 2.0.5no fix listednot listed
moonjit_project moonjitbefore 2.1.2fixed in 2.1.22.1.2

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources