CVE Vulnerability

CVE-2019-19391

** DISPUTED ** 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.

6.4 /10

CVSS v2.0 :

V3 Legend

Vector :

Exploitability : 10 / Impact : 4.9

Attack Vector

Attack Complexity

Privileges Required

User Interaction

Confidentiality Impact PARTIAL

Integrity Impact PARTIAL

Availability Impact NONE

Scope

9.1 /10

CVSS v3.0 : CRITICAL

V3 Legend

Vector :

Exploitability : 3.9 / Impact : 5.2

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact NONE

Scope UNCHANGED

References
Link Resource
https://github.com/LuaJIT/LuaJIT/pull/526 Issue Tracking Patch
Configurations

Configuration 1

cpe:2.3:a:luajit:luajit:*:*:*:*:*:*:*:*
cpe:2.3:a:moonjit_project:moonjit:*:*:*:*:*:*:*:*
Information

Published : 2019-11-29 04:15

Updated : 2019-12-19 06:45

NVD link : CVE-2019-19391

Mitre link : CVE-2019-19391

Products Affected
No products.
CWE
CWE-843