ggerganov llama.cpp gguf_init_from_file missing initialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in ggerganov llama.cpp. The impacted element is the function gguf_init_from_file. Performing a manipulation results in missing initialization.
This vulnerability was named CVE-2024-32878. The attack may be initiated remotely. There is no available exploit.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability was found in ggerganov llama.cpp (the affected version is unknown). It has been classified as problematic. This affects the function gguf_init_from_file. The manipulation with an unknown input leads to a missing initialization vulnerability. CWE is classifying the issue as CWE-456. The product does not initialize critical variables, which causes the execution environment to use unexpected values. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Llama.cpp is LLM inference in C/C++. There is a use of uninitialized heap variable vulnerability in gguf_init_from_file, the code will free this uninitialized variable later. In a simple POC, it will directly cause a crash. If the file is carefully constructed, it may be possible to control this uninitialized value and cause arbitrary address free problems. This may further lead to be exploited. Causes llama.cpp to crash (DoS) and may even lead to arbitrary code execution (RCE). This vulnerability has been patched in commit b2740.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-32878 since 04/19/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Applying the patch b2740 is able to eliminate this problem.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CNA Base Score: 7.1
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Missing initializationCWE: CWE-456 / CWE-453
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Upgrade: github.com
Patch: b2740
Timeline
04/19/2024 🔍04/26/2024 🔍
04/26/2024 🔍
09/02/2025 🔍
Sources
Product: github.comAdvisory: GHSA-p5mv-gjc5-mwqv
Status: Confirmed
CVE: CVE-2024-32878 (🔍)
GCVE (CVE): GCVE-0-2024-32878
GCVE (VulDB): GCVE-100-262203
Entry
Created: 04/26/2024 23:06Updated: 09/02/2025 21:02
Changes: 04/26/2024 23:06 (61), 05/30/2024 14:53 (2), 05/30/2024 14:57 (1), 09/02/2025 21:02 (13)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.