LuaJIT up to 2.1 lj_state.c out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in LuaJIT up to 2.1. Impacted is an unknown function of the file lj_state.c. The manipulation leads to out-of-bounds. This vulnerability is documented as CVE-2024-25178. There is not any exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in LuaJIT up to 2.1 and classified as critical. This issue affects an unknown code of the file lj_state.c. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

LuaJIT through 2.1 has an out-of-bounds read in the stack-overflow handler in lj_state.c

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-25178 since 02/07/2024. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 242859 (Azure Linux 3.0 Security Update: luajit / sysbench (CVE-2024-25178)), which helps to determine the existence of the flaw in a target environment.

Applying the patch defe61a56751a0db5f00ff3ab7b8f45436ba74c8 is able to eliminate this problem. The bugfix is ready for download at github.com.

The vulnerability is also documented in the databases at Tenable (242859) and EUVD (EUVD-2024-22514). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 242859
Nessus Name: Azure Linux 3.0 Security Update: luajit / sysbench (CVE-2024-25178)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔒

Patch: defe61a56751a0db5f00ff3ab7b8f45436ba74c8

Timelineinfo

02/07/2024 CVE reserved
07/07/2025 +515 days Advisory disclosed
07/07/2025 +0 days VulDB entry created
07/26/2025 +19 days VulDB entry last update

Sourcesinfo

Product: github.com

Advisory: 1152
Status: Confirmed

CVE: CVE-2024-25178 (🔒)
GCVE (CVE): GCVE-0-2024-25178
GCVE (VulDB): GCVE-100-315221
EUVD: 🔒

Entryinfo

Created: 07/07/2025 20:29
Updated: 07/26/2025 15:28
Changes: 07/07/2025 20:29 (56), 07/24/2025 20:26 (1), 07/25/2025 02:42 (1), 07/26/2025 15:28 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!