Learn about CVE-2019-19391 affecting LuaJIT versions up to 2.0.5, including Moonjit before 2.1.2. Understand the type confusion issue in the debug.getinfo function and its impact.
LuaJIT versions up to 2.0.5, including Moonjit before 2.1.2, and related products have a type confusion issue in the debug.getinfo function. Although the LuaJIT project owner does not consider it a vulnerability, it can lead to unauthorized memory accesses.
Understanding CVE-2019-19391
In LuaJIT and related products, a type confusion issue in the debug.getinfo function can potentially result in unauthorized memory accesses due to mishandling certain cases involving valid stack levels and options.
What is CVE-2019-19391?
The type confusion issue in LuaJIT versions up to 2.0.5, including Moonjit prior to 2.1.2, and other related products, allows for unauthorized memory writes or reads due to mishandling specific cases involving valid stack levels and options.
The Impact of CVE-2019-19391
The issue can lead to unauthorized memory writes or reads, potentially resulting in security vulnerabilities. The LuaJIT project owner considers the debug library inherently unsafe, hence not recognizing this as a vulnerability.
Technical Details of CVE-2019-19391
In LuaJIT and related products, the following technical details are relevant:
Vulnerability Description
The type confusion issue within the debug.getinfo function can lead to unauthorized memory accesses.
Affected Systems and Versions
Exploitation Mechanism
The issue arises due to mishandling certain cases involving valid stack levels and options, allowing for unauthorized memory accesses.
Mitigation and Prevention
To address CVE-2019-19391, consider the following steps:
Immediate Steps to Take
Long-Term Security Practices
Patching and Updates