Lua vulnerabilitiesNone on the known-exploited list.
Lua has 17 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Lua, with 17. If you run Lua software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Lua products have the most vulnerabilities?
Lua leads with 17 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Lua vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Lua's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Lua flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 17%CVE-2019-6706High
Lua 5.3.5 has a use-after-free in lua_upvaluejoin in lapi.c.
- 12%CVE-2014-5461Medium
Buffer overflow in the vararg functions in ldo.c in Lua 5.1 through 5.2.x before 5.2.3 allows context-dependent attackers to cause a denial of service (crash) via a small number of arguments to a function with a...
- 3.8%CVE-2020-24370Medium
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).
- 3.0%CVE-2022-28805Critical
singlevar 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-based buffer over-read that might affect a system that compiles untrusted Lua code.
- 2.8%CVE-2022-33099High
An issue in the component luaG_runerror of Lua v5.4.4 and below leads to a heap-buffer overflow when a recursive error occurs.
- 2.4%CVE-2020-15888High
Lua through 5.4.0 mishandles the interaction between stack resizes and garbage collection, leading to a heap-based buffer overflow, heap-based buffer over-read, or use-after-free.
- 2.2%CVE-2020-15889Critical
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.
- 2.1%CVE-2021-32918High
An issue was discovered in Prosody before 0.11.9.
- 1.7%CVE-2020-24371Medium
lgc.c in Lua 5.4.0 mishandles the interaction between barriers and the sweep phase, leading to a memory access violation involving collectgarbage.
- 1.7%CVE-2020-24369High
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.
All Lua products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Lua? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Lua 5.3.5 has a use-after-free in lua_upvaluejoin in lapi.c. For example, a crash outcome might be achieved by an attacker who is able to trigger a debug.upvaluejoin call in which the arguments have certain relationships.
- Matched to
- Lua on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 17 published vulnerabilities across 1 product and 40 versions from Lua.
None of Lua's vulnerabilities is on the list of flaws known to be exploited today.
Lua, with 17 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Lua products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.