CVE-2021-43519: Stack overflow in lua_resume of ldo.c in Lua Interpreter 5.1.0~5.4.4 allows attackers to perform a Denial of Service via a crafted script fi
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 68.8% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: lua (AlmaLinux:9) 5.4.4-2.el9_1; lua-devel (AlmaLinux:9) 5.4.4-2.el9_1; lua-libs (AlmaLinux:9) 5.4.4-2.el9_1.
Low priority for now. Upgrade to lua (AlmaLinux:9) 5.4.4-2.el9_1; lua-devel (AlmaLinux:9) 5.4.4-2.el9_1; lua-libs (AlmaLinux:9) 5.4.4-2.el9_1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Stack overflow in lua_resume of ldo.c in Lua Interpreter 5.1.0~5.4.4 allows attackers to perform a Denial of Service via a crafted script file.
- Published
- Nov 9, 2021
- Updated
- Jun 17, 2026
- EPSS
- 1.2% · 68th percentile
- CWE
- CWE-674
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| lua | lua | cpe:2.3:a:lua:lua |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora35
- lua lua5.1.0 and later · before 5.3.5
- lua lua5.4.0 and later · before 5.4.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | lua | before 5.4.4-2.el9_1 | 5.4.4-2.el9_1 |
| AlmaLinux:9 | lua-devel | before 5.4.4-2.el9_1 | 5.4.4-2.el9_1 |
| AlmaLinux:9 | lua-libs | before 5.4.4-2.el9_1 | 5.4.4-2.el9_1 |
| Debian:12 | lua5.4 | before 5.4.4-1 | 5.4.4-1 |
| openSUSE:Tumbleweed | lua55 | before 5.5.0~beta1-1.1 | 5.5.0~beta1-1.1 |
| Red Hat:enterprise_linux:9::appstream | lua | before 0:5.4.4-2.el9_1 | 0:5.4.4-2.el9_1 |
| Red Hat:enterprise_linux:9::appstream | lua-debuginfo | before 0:5.4.4-2.el9_1 | 0:5.4.4-2.el9_1 |
| Red Hat:enterprise_linux:9::appstream | lua-debugsource | before 0:5.4.4-2.el9_1 | 0:5.4.4-2.el9_1 |
| Red Hat:enterprise_linux:9::appstream | lua-libs-debuginfo | before 0:5.4.4-2.el9_1 | 0:5.4.4-2.el9_1 |
| Red Hat:enterprise_linux:9::baseos | lua-libs | before 0:5.4.4-2.el9_1 | 0:5.4.4-2.el9_1 |
| Red Hat:enterprise_linux:9::crb | lua-devel | before 0:5.4.4-2.el9_1 | 0:5.4.4-2.el9_1 |
| Red Hat:rhel_eus:9.0::appstream | lua | before 0:5.4.4-1.el9_0.1 | 0:5.4.4-1.el9_0.1 |
| Red Hat:rhel_eus:9.0::appstream | lua-debuginfo | before 0:5.4.4-1.el9_0.1 | 0:5.4.4-1.el9_0.1 |
| Red Hat:rhel_eus:9.0::appstream | lua-debugsource | before 0:5.4.4-1.el9_0.1 | 0:5.4.4-1.el9_0.1 |
| Red Hat:rhel_eus:9.0::appstream | lua-libs-debuginfo | before 0:5.4.4-1.el9_0.1 | 0:5.4.4-1.el9_0.1 |
| Red Hat:rhel_eus:9.0::baseos | lua-libs | before 0:5.4.4-1.el9_0.1 | 0:5.4.4-1.el9_0.1 |
| Red Hat:rhel_eus:9.0::crb | lua-devel | before 0:5.4.4-1.el9_0.1 | 0:5.4.4-1.el9_0.1 |
| Rocky Linux:9 | lua | before 0:5.4.4-2.el9_1 | 0:5.4.4-2.el9_1 |
Same product
lua: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-15889Lua 5.4.0 has a getobjname heap-based buffer over-read because youngcollection in lgc.c uses markold for an insufficient number of list memb40Plan
- CVE-2022-28805singlevar in lparser.c in Lua from (including) 5.4.0 up to (excluding) 5.4.4 lacks a certain luaK_exp2anyregup call, leading to a heap-based37Monitor
- CVE-2020-15888Lua through 5.4.0 mishandles the interaction between stack resizes and garbage collection, leading to a heap-based buffer overflow, heap-bas36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-24370Aug 17, 2020 · ldebug.c in Lua 5.4.0 allows a negation overflow and segmentation fault in getlocal and setlocal, as demonstrated by getlocal(3,2^31).22Monitor
- ← EarlierCVE-2020-24371Aug 17, 2020 · lgc.c in Lua 5.4.0 mishandles the interaction between barriers and the sweep phase, leading to a memory access violation involving collectga22Monitor
- Later →CVE-2021-44647Jan 11, 2022 · Lua v5.4.3 and above are affected by SEGV by type confusion in funcnamefromcode function in ldebug.c which can cause a local denial of servi22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:lua | 5.4.4-2.el9_1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:lua-devel | 5.4.4-2.el9_1 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:lua-libs | 5.4.4-2.el9_1 · AlmaLinux:9 | Package registry (OSV) |
| debian:lua5.4 | 5.4.4-1 · Debian:12 | Package registry (OSV) |
| opensuse:lua55 | 5.5.0~beta1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:lua | 0:5.4.4-2.el9_1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:lua-debuginfo | 0:5.4.4-2.el9_1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:lua-debugsource | 0:5.4.4-2.el9_1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:lua-devel | 0:5.4.4-2.el9_1 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| red hat:lua-libs | 0:5.4.4-2.el9_1 · Red Hat:enterprise_linux:9::baseos | Package registry (OSV) |
| red hat:lua-libs-debuginfo | 0:5.4.4-2.el9_1 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| rocky linux:lua | 0:5.4.4-2.el9_1 · Rocky Linux:9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-674 · Uncontrolled RecursionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.