Skip to content
Fencer Vulns
critical 9.8

CVE-2020-15889 json

Lua 5.4.0 has a getobjname heap-based buffer over-read because youngcollection in lgc.c uses markold for an insufficient number of list mem…

published 2020-07-21 6 y ago modified 2026-09-08 2 mo ago also BIT-lua-2020-15889 , EUVD-2020-7863

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

Summary

Lua 5.4.0 has a getobjname heap-based buffer over-read because youngcollection in lgc.c uses markold for an insufficient number of list members.

Patch / fix

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

debian advisories DEBIAN-CVE-2020-15889

  • lua Arch Linux 5.4.1-1

arch linux advisories AVG-1207

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-15889 updated cvss 8.1

lua: heap-based buffer over-read in lgc.c

  • Red Hat Enterprise Linux 6 lua Red Hat Enterprise Linux 7 lua Red Hat Enterprise Linux 8 lua, lua-libs Red Hat Enterprise Linux 9 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

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

Exploits and checks

  • lua-users.org http://lua-users.org/lists/lua-l/2020-07/msg00078.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.