Security readout for executives and security teams
Plain-English summary
CVE-2020-24372 is an out-of-bounds read in LuaJIT through 2.1.0-beta3. The source bundle does not provide a CVSS score, detailed impact, or confirmed exploit activity. Treat exposure seriously where LuaJIT processes untrusted Lua code or is embedded in business applications.
Executive priority
Handle as a targeted dependency remediation item, not an emergency based on current evidence. Prioritize externally exposed, plugin-enabled, or script-execution environments first, and require teams to prove whether LuaJIT is present.
Technical view
The CVE describes an out-of-bounds read in lj_err_run in lj_err.c affecting LuaJIT through 2.1.0-beta3. Available metadata lacks CWE, CVSS, affected CPEs, and exploit confirmation. The GitHub issue and Debian LTS advisory are the main remediation references.
Likely exposure
Exposure is likely limited to systems running or embedding LuaJIT through 2.1.0-beta3. Confirm direct packages, vendored source copies, containers, and applications that bundle LuaJIT rather than relying only on package-manager inventory.
Exploitation context
No source in the bundle confirms active exploitation, and the CVE is not listed as KEV. The issue is a memory-safety bug report, but the provided evidence does not establish exploitability, exploit maturity, or real-world targeting.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, patch version, or exploit status is supplied. Analysis should center on confirming LuaJIT version presence, embedded copies, and whether untrusted Lua can trigger the affected error path.
Mitigation direction
- Inventory LuaJIT packages and embedded copies across applications and containers.
- Check LuaJIT issue 603 and vendor advisories for fixed or recommended versions.
- Apply Debian LTS or distribution package updates where applicable.
- Prioritize systems that execute user-supplied Lua code or plugins.
- If updates are unavailable, restrict untrusted Lua execution pending vendor guidance.
Validation and detection
- Identify installed LuaJIT versions and confirm whether they are through 2.1.0-beta3.
- Search source trees and build artifacts for vendored LuaJIT copies.
- Verify distribution advisory applicability for deployed operating system releases.
- Confirm remediation by rechecking package versions after updates.
- Review application paths where untrusted Lua code can reach LuaJIT error handling.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2020-24372 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/LuaJIT/LuaJIT/issues/603CVE reference · x_refsource_MISC
- https://lists.debian.org/debian-lts-announce/2025/08/msg00022.htmlCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.