Skip to content
Fencer Vulns
high 7.5

CVE-2020-24369 json

ldebug.c in Lua 5.4.0 attempts to access debug information via the line hook of a stripped function, leading to a NULL pointer dereference.

published 2020-08-17 6 y ago modified 2026-09-08 2 mo ago also BIT-lua-2020-24369 , EUVD-2020-17101

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

ldebug.c in Lua 5.4.0 attempts to access debug information via the line hook of a stripped function, leading to a NULL pointer dereference.

Patch / fix

  • bitnami lua 5.4.1
  • lua5.4 Debian 14, Debian 13, Debian 12 5.4.1-1

debian advisories DEBIAN-CVE-2020-24369

  • lua55 openSUSE Tumbleweed 5.5.0~beta1-1.1

opensuse advisories openSUSE-SU-2025:15401-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-24369 updated cvss 7.0

lua: NULL pointer dereference when trying to access debug information via the line hook of a stripped function

  • Red Hat Enterprise Linux 6 lua Red Hat Enterprise Linux 7 lua Red Hat Enterprise Linux 8 lua, lua-libs
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.68% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • lua.org https://www.lua.org/bugs.html#5.4.0-12 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami lua
>=5.4.0, <5.4.1
5.4.1

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.