{"api_version":"1","generated_at":"2026-07-23T11:18:05+00:00","cve":"CVE-2019-19391","urls":{"html":"https://cve.report/CVE-2019-19391","api":"https://cve.report/api/cve/CVE-2019-19391.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2019-19391","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-19391"},"summary":{"title":"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 > 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.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2019-11-29 16:15:00","updated_at":"2023-11-07 03:07:00"},"problem_types":["CWE-843"],"metrics":[],"references":[{"url":"https://github.com/LuaJIT/LuaJIT/pull/526","name":"https://github.com/LuaJIT/LuaJIT/pull/526","refsource":"MISC","tags":["Issue Tracking","Patch","Third Party Advisory"],"title":"debug.getinfo arbitrary memory read/write by Badger9 · Pull Request #526 · LuaJIT/LuaJIT · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-19391","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-19391","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2019","cve_id":"19391","vulnerable":"1","versionEndIncluding":"2.0.5","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"luajit","cpe5":"luajit","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2019","cve_id":"19391","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"moonjit_project","cpe5":"moonjit","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2019","cve_id":"19391","vulnerable":"1","versionEndIncluding":"1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"moonjit_project","cpe5":"moonjit","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2019-19391","qid":"904819","title":"Common Base Linux Mariner (CBL-Mariner) Security Update for fluent-bit (12327)"},{"cve":"CVE-2019-19391","qid":"905172","title":"Common Base Linux Mariner (CBL-Mariner) Security Update for sysbench (12653)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2019-19391","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"** 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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"url":"https://github.com/LuaJIT/LuaJIT/pull/526","refsource":"MISC","name":"https://github.com/LuaJIT/LuaJIT/pull/526"}]}},"nvd":{"publishedDate":"2019-11-29 16:15:00","lastModifiedDate":"2023-11-07 03:07:00","problem_types":["CWE-843"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE","baseScore":9.1,"baseSeverity":"CRITICAL"},"exploitabilityScore":3.9,"impactScore":5.2},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:P/I:P/A:N","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":6.4},"severity":"MEDIUM","exploitabilityScore":10,"impactScore":4.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:luajit:luajit:*:*:*:*:*:*:*:*","versionEndIncluding":"2.0.5","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:moonjit_project:moonjit:*:*:*:*:*:*:*:*","versionEndExcluding":"2.1.2","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2019","CveId":"19391","Ordinal":"161038","Title":"CVE-2019-19391","CVE":"CVE-2019-19391","Year":"2019"},"notes":[{"CveYear":"2019","CveId":"19391","Ordinal":"1","NoteData":"** 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.","Type":"Description","Title":null},{"CveYear":"2019","CveId":"19391","Ordinal":"2","NoteData":"2019-11-29","Type":"Other","Title":"Published"},{"CveYear":"2019","CveId":"19391","Ordinal":"3","NoteData":"2019-12-04","Type":"Other","Title":"Modified"}]}}}