Access of Resource Using Incompatible Type ('Type Confusion') Affecting luajit package, versions *


Severity

Recommended
low

Based on Debian security rating.

Threat Intelligence

EPSS
0.13% (49th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Access of Resource Using Incompatible Type ('Type Confusion') vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIAN11-LUAJIT-536469
  • published3 Dec 2019
  • disclosed29 Nov 2019

Introduced: 29 Nov 2019

CVE-2019-19391  (opens in a new tab)
CWE-843  (opens in a new tab)

How to fix?

There is no fixed version for Debian:11 luajit.

NVD Description

Note: Versions mentioned in the description apply only to the upstream luajit package and not the luajit package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

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

CVSS Scores

version 3.1