CVE-2024-25176

Exp

LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240626 have a stack-buffer-overflow in lj_strfmt_wfnum in lj_strfmt_num.c.

Published: 2025-07-07 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-25176 is rated High Exploit Risk (79.6/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.69%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-25176

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-25176

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-04 0.58% 0.69% +0.11%
2 2026-05-03 0.17% 0.58% +0.41%
3 2026-03-23 — 0.17% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-25176

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-25176

OS Trackers for CVE-2024-25176

vendor priority summary link
alpine — CVE-2024-25176: 1 source package rows (luajit); 10 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 6, open 4. https://security.alpinelinux.org/vuln/CVE-2024-25176
debian not yet assigned CVE-2024-25176 not yet assigned priority: Debian including 1 source packages (luajit), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-25176
redhat low — https://access.redhat.com/security/cve/CVE-2024-25176
suse low CVE-2024-25176 severity low: SUSE including 9 source package names (libluajit-5_1-2, libluajit-5_1-2-2.1.0~beta3+git.1624618403.e9577376-150400.4.5.1, …), 16 product×package rows across 7 product lines (SUSE Linux Enterprise Module for Basesystem 15 SP6, SUSE Linux Enterprise Module for Basesystem 15 SP7, … (7 product lines)): Fixed 13, Known Not Affected 3. https://www.suse.com/security/cve/CVE-2024-25176/
ubuntu medium CVE-2024-25176 medium priority: Ubuntu including 1 source packages (luajit), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 8, ignored 2. https://ubuntu.com/security/CVE-2024-25176

Affected software / configurations for CVE-2024-25176

Vendor Product Version Raw CPE
luajit luajit <= 2.1.0 cpe:2.3:a:luajit:luajit:*:*:*:*:*:*:*:*

References for CVE-2024-25176

cvelogic Threat Intelligence