{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-19391 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-19391 is a critical memory corruption vulnerability in n/a, published on 29 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19391 and fix it if it is affected.\n\nWhat it is: CVE-2019-19391 is a critical memory corruption vulnerability in n/a, published on 29 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-19391 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-19391/ (Markdown: https://insights.sbomify.com/CVE-2019-19391/index.md)","id":"CVE-2019-19391","markdown":"https://insights.sbomify.com/CVE-2019-19391/index.md","name":"CVE-2019-19391","record":{"aliases":["AZL-41306","DEBIAN-CVE-2019-19391","GHSA-756f-h55r-pvqq","openSUSE-SU-2024:13922-1","openSUSE-SU-2025:15672-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"LuaJIT library","requires_auth":"none","summary":"Type confusion in LuaJIT debug.getinfo allows arbitrary memory read or write, potentially leading to code execution or data disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"luajit","vendor":"luajit"},{"product":"moonjit","vendor":"moonjit_project"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"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","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2019-19391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2019"},"n_packages":1,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-19392"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["2.1.20250826-1.1"],"introduced":["0"],"last_affected":[],"package":"luajit","purl":"pkg:rpm/opensuse/luajit\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15672-1"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19390"},"products":["n/a"],"published":"2019-11-29","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-25176","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2024-25178","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2024-25177","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2020-24372","kev_date_added":null,"published":"2020-08-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-03","vendors":["n/a"]},"summary":"Type confusion in LuaJIT debug.getinfo allows arbitrary memory read or write, potentially leading to code execution or data disclosure.","url":"https://insights.sbomify.com/CVE-2019-19391/"}