Upstream information

CVE-2019-19391 at MITRE


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

SUSE information

Overall state of this security issue: Running

This issue is currently rated as having moderate severity.

CVSS v2 Scores
  National Vulnerability Database
Base Score 6.4
Vector AV:N/AC:L/Au:N/C:P/I:P/A:N
Access Vector Network
Access Complexity Low
Authentication None
Confidentiality Impact Partial
Integrity Impact Partial
Availability Impact None
CVSS v3 Scores
  National Vulnerability Database
Base Score 9.1
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Attack Vector Network
Attack Complexity Low
Privileges Required None
User Interaction None
Scope Unchanged
Confidentiality Impact High
Integrity Impact High
Availability Impact None
CVSSv3 Version 3.1
No SUSE Bugzilla entries cross referenced.

SUSE Security Advisories:

List of released packages

Product(s) Fixed package version(s) References
Container caasp/v4/cilium:1.6.6
  • libluajit-5_1-2 >= 2.1.2-1.3.1
  • libre2-0 >= 20200101-1.3.1
  • libsqlparser1 >= 1.5+git20181206-1.3.1
SUSE Package Hub 12
  • libluajit-5_1-2 >= 2.1.2-2.1
  • moonjit >= 2.1.2-2.1
  • moonjit-devel >= 2.1.2-2.1

SUSE Timeline for this CVE

CVE page created: Tue Dec 3 17:27:52 2019
CVE page last modified: Tue May 23 15:24:20 2023