CVE-2019-19391

Critical

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

SeverityCritical
CVSS9.1
Exploit probability—
ProductLuajit
PublishedNov 29, 2019
First seenNov 29, 2019

How to fix

Update
  • moonjit_project moonjit2.1.2 or later

Affected products

ProductAffected versionsFixed in
luajit luajitv ≤ 2.0.5—
moonjit_project moonjitv < 2.1.22.1.2

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2019-19391 · Luajit · Dark Radar