LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15890: LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled.

LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

LuaJIT through 2.1.0-beta3 can read memory outside intended bounds when handling garbage-collection finalizer frame traversal. Business impact is uncertain from the supplied sources, but memory-safety bugs in language runtimes matter when the runtime is embedded in applications or exposed to attacker-influenced scripts.

Executive priority

Treat this as a targeted dependency remediation item, not an emergency based on current evidence. Prioritize internet-facing or multi-tenant systems that execute LuaJIT code, then complete routine package and embedded dependency updates.

Technical view

CVE-2020-15890 is an out-of-bounds read in LuaJIT caused by mishandled __gc handler frame traversal. The public bundle identifies LuaJIT through 2.1.0-beta3 and includes Debian and Ubuntu security updates. No CVSS, CWE, or detailed exploitation prerequisites are provided.

Likely exposure

Exposure is most likely in systems that package, embed, or depend on LuaJIT, especially where Lua code can be influenced by users or plugins. The bundle specifically includes Debian and Ubuntu advisories, but does not enumerate all affected downstream products.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source claims active exploitation. The sources do not provide exploit maturity, attack complexity, or whether remote exploitation is possible in common deployments.

Researcher notes

The key uncertainty is exploitability in real applications. The bundle establishes an out-of-bounds read and affected LuaJIT range, but not CVSS, CWE, fixed upstream release detail, or proof of active exploitation. Downstream distro advisories are important for remediation confirmation.

Mitigation direction

  • Apply relevant Debian or Ubuntu LuaJIT security updates where applicable.
  • For source builds, review LuaJIT issue 601 and vendor guidance before updating.
  • Inventory applications that embed LuaJIT, not only OS packages.
  • Restrict untrusted Lua script execution until affected runtimes are updated.

Validation and detection

  • Identify installed or embedded LuaJIT versions across hosts and applications.
  • Flag LuaJIT versions through 2.1.0-beta3 for remediation review.
  • Compare distro packages against Debian DLA 2296-1 and Ubuntu USN-4501-1 guidance.
  • Confirm whether any application runs attacker-influenced Lua code.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2020-15890 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.