ubuntu-cve-2019-19391
Vulnerability from osv_ubuntu
Published
2019-11-29 16:15
Modified
2025-07-16 04:55
Summary
Details

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

Severity
9.1 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
N/A (UNKNOWN)
low
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "availability": "No subscription required",
        "binaries": [
          {
            "binary_name": "libluajit-5.1-2",
            "binary_version": "2.1.0+git20231223.c525bcb+dfsg-1"
          },
          {
            "binary_name": "libluajit-5.1-2-dbgsym",
            "binary_version": "2.1.0+git20231223.c525bcb+dfsg-1"
          },
          {
            "binary_name": "libluajit-5.1-common",
            "binary_version": "2.1.0+git20231223.c525bcb+dfsg-1"
          },
          {
            "binary_name": "libluajit-5.1-dev",
            "binary_version": "2.1.0+git20231223.c525bcb+dfsg-1"
          },
          {
            "binary_name": "luajit",
            "binary_version": "2.1.0+git20231223.c525bcb+dfsg-1"
          },
          {
            "binary_name": "luajit-dbgsym",
            "binary_version": "2.1.0+git20231223.c525bcb+dfsg-1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "luajit",
        "purl": "pkg:deb/ubuntu/luajit@2.1.0+git20231223.c525bcb+dfsg-1?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.1.0+git20231223.c525bcb+dfsg-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.1.0~beta3+git20220320+dfsg-4.1",
        "2.1.0+git20231223.c525bcb+dfsg-1~build1"
      ]
    }
  ],
  "aliases": [],
  "details": "** 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 \u003e 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.",
  "id": "UBUNTU-CVE-2019-19391",
  "modified": "2025-07-16T04:55:13Z",
  "published": "2019-11-29T16:15:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2019-19391"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/LuaJIT/LuaJIT/pull/526"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2019-19391"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "low",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2019-19391"
  ],
  "withdrawn": "2025-07-18T16:45:29Z"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.