CVE-2024-25177
Luajit NULL pointer dereference
- Published7 Jul 2025
Description
LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an unsinking of IR_FSTORE for NULL metatable, which leads to Denial of Service (DoS).
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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/a73f560d79f2c3d4011d6c5a2676f04a
- https://github.com/LuaJIT/LuaJIT/commit/85b4fed0b0353dd78c8c875c2f562d522a2b310f
- https://github.com/LuaJIT/LuaJIT/issues/1147
- https://github.com/openresty/luajit2/commit/85b4fed0b0353dd78c8c875c2f562d522a2b310f
- 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-25177 being actively exploited?
CVE-2024-25177 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.53%.
How severe is CVE-2024-25177?
CVE-2024-25177 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.53% probability of exploitation.
Which products are affected by CVE-2024-25177?
Affected products include Luajit.
How do I fix CVE-2024-25177?
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-25177 against the real software inventory on every managed device, every day. 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.