{"id":"CVE-2019-19391","aliases":["AZL-41306","BELL-CVE-2019-19391","DEBIAN-CVE-2019-19391","DLA-4283-1","EUVD-2019-9012","GHSA-756f-h55r-pvqq","MGASA-2026-0225","UBUNTU-CVE-2019-19391","openSUSE-SU-2024:13922-1","openSUSE-SU-2025:15672-1"],"status":"disputed","title":"In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a...","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 \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","severity":{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.01396,"percentile":0.72764,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-843"],"published":"2019-11-29T15:18:49Z","modified":"2026-11-05T05:40:51Z","fixes":[{"ecosystem":"Azure Linux:3","package":"sysbench","fixed_in":["1.0.20-3"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"luajit","fixed_in":["2.1.0~beta3+git20210112+dfsg-2"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"luajit","fixed_in":["2.1.0~beta3+git20210112+dfsg-2"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"luajit","fixed_in":["2.1.0~beta3+git20210112+dfsg-2"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"luajit","fixed_in":["2.1.20250826-1.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"sysbench","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.20-3"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"luajit","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0~beta3+git20210112+dfsg-2"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"luajit","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0~beta3+git20210112+dfsg-2"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"luajit","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0~beta3+git20210112+dfsg-2"}]}]},{"source":"osv","ecosystem":"Debian:11","package":"luajit","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0~beta3+dfsg-5.3+deb11u1"}]}],"versions":["2.1.0~beta3+dfsg-5.3"],"bundled":6},{"source":"osv","ecosystem":"Mageia:9","package":"luajit","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.0-0.beta3.10.1.mga9"}]}],"bundled":5},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"luajit","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.20250826-1.1"}]}]}],"products":[{"vendor":"luajit","product":"luajit"},{"vendor":"moonjit_project","product":"moonjit"}],"references":[{"url":"https://github.com/LuaJIT/LuaJIT/pull/526","tags":["x_refsource_MISC","x_transferred","Issue Tracking","Patch","Third Party Advisory","fix","report"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/08/msg00022.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-19391","tags":["web"]},{"url":"https://github.com/advisories/GHSA-756f-h55r-pvqq"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2019-19391","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2019-19391","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0225.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=34491","tags":["report"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XU3NWLH45W4F7OBKEB4XEOJQI4S36PU5/","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2019-19391","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-19391","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2019-19391","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2019-19391","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 \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","status":"disputed","published":"2019-11-29T15:18:49Z","modified":"2025-11-03T18:07:53.427Z","updated_at":"2026-11-02T14:20:21.059499Z"}],"euvd":[{"id":"EUVD-2019-9012","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 \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","status":"published","published":"2019-11-29T15:18:49Z","modified":"2025-11-03T18:07:53Z","updated_at":"2026-11-02T19:49:35.000596Z"}],"ghsa":[{"id":"GHSA-756f-h55r-pvqq","title":"In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a...","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 \u003e options are mishandled.","status":"published","published":"2022-05-24T17:02:27Z","modified":"2025-11-03T21:30:31Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T15:04:18.176646Z"}],"nvd":[{"id":"CVE-2019-19391","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 \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","status":"disputed","published":"2019-11-29T16:15:10.577Z","modified":"2026-06-17T02:26:37.077Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical","assessor":"primary"},{"version":"2.0","score":6.4,"vector":"AV:N/AC:L/Au:N/C:P/I:P/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-843"],"updated_at":"2026-11-02T14:05:38.993437Z"}],"osv":[{"id":"AZL-41306","title":"CVE-2019-19391 affecting package sysbench for versions less than 1.0.20-3","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 \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","status":"published","published":"2019-11-29T16:15:10Z","modified":"2026-11-05T05:40:51Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-05T16:41:19.893001Z"},{"id":"BELL-CVE-2019-19391","title":"CVE-2019-19391 does not affect BellSoft software","status":"withdrawn","published":"2019-11-29T16:15:00Z","modified":"2026-01-26T09:45:40.149358Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:28:15.340685Z"},{"id":"CVE-2019-19391","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 \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","status":"published","published":"2019-11-29T16:15:10.577Z","modified":"2026-11-04T02:45:22.926384121Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-04T02:54:44.889498Z"},{"id":"DEBIAN-CVE-2019-19391","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 \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","status":"published","published":"2019-11-29T16:15:10.577Z","modified":"2026-09-21T07:02:54.651163866Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:45:32.221385Z"},{"id":"UBUNTU-CVE-2019-19391","description":"** 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.","status":"withdrawn","published":"2019-11-29T16:15:00Z","modified":"2025-07-16T08:14:34.327824Z","cvss":[{"version":"3.1","score":9.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","level":"critical"}],"updated_at":"2026-11-02T15:54:20.325378Z"},{"id":"DLA-4283-1","title":"luajit - security update","status":"published","published":"2025-08-25T00:00:00Z","modified":"2026-03-09T02:09:10.584174Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"MGASA-2026-0225","title":"Updated luajit packages fix security vulnerabilities","description":"In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other\nproducts, debug.getinfo has a type confusion issue that leads to\narbitrary memory write or read operations, because certain cases\ninvolving valid stack levels and \u003e options are mishandled.\n(CVE-2019-19391)\nLuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in\nlj_err.c. (CVE-2020-24372)\nLuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240626 have a\nstack-buffer-overflow in lj_strfmt_wfnum in lj_strfmt_num.c.\n(CVE-2024-25176)\nLuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an\nunsinking of IR_FSTORE for NULL metatable, which leads to Denial of\nService (DoS). (CVE-2024-25177)\nLuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an\nout-of-bounds read in the stack-overflow handler in lj_state.c.\n(CVE-2024-25178)\n","status":"published","published":"2026-06-18T21:28:22Z","modified":"2026-06-18T21:30:04.565170803Z","updated_at":"2026-11-02T15:49:43.795591Z"},{"id":"openSUSE-SU-2024:13922-1","title":"libluajit2-5_1-2-2.1.20240314-1.1 on GA media","description":"These are all security issues fixed in the libluajit2-5_1-2-2.1.20240314-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T04:07:47.046847Z","updated_at":"2026-11-02T16:58:36.662953Z"},{"id":"openSUSE-SU-2025:15672-1","title":"libluajit-5_1-2-2.1.20250826-1.1 on GA media","description":"These are all security issues fixed in the libluajit-5_1-2-2.1.20250826-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-10-27T00:00:00Z","modified":"2026-03-23T04:54:04.952277Z","updated_at":"2026-11-02T16:58:37.810934Z"}]}}