CVE-2024-25178
Luajit out-of-bounds read
- Published7 Jul 2025
Description
LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://gist.github.com/pwnhacker0x18/423b4292f301ab274b42d5ed6e0b87d8
- https://github.com/LuaJIT/LuaJIT/commit/defe61a56751a0db5f00ff3ab7b8f45436ba74c8
- https://github.com/LuaJIT/LuaJIT/issues/1152
- https://github.com/openresty/luajit2/commit/defe61a56751a0db5f00ff3ab7b8f45436ba74c8
- https://lists.debian.org/debian-lts-announce/2025/08/msg00022.html
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-25178 being actively exploited?
CVE-2024-25178 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.66%.
How severe is CVE-2024-25178?
CVE-2024-25178 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.66% probability of exploitation.
Which products are affected by CVE-2024-25178?
Affected products include Luajit.
How do I fix CVE-2024-25178?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-25178 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.