CVE-2024-32878: high-severity vulnerability in ggerganov llama.cpp
Use of Uninitialized Variable Vulnerability in llama.cpp
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.7%
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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L
Affected products
ggerganov · llama.cppRelated CVEs — ggerganov llama.cpp
In the same product, most dangerous first.
CVE-2024-42479CRITICALllama.cpp allows write-what-where in rpc_server::set_tensorEPSS 2.6%CVE-2024-42478MEDIUMllama.cpp allows Arbitrary Address Read in rpc_server::get_tensorEPSS 0.6%CVE-2024-42477MEDIUMllama.cpp global-buffer-overflow in ggml_type_sizeEPSS 0.5%CVE-2024-41130MEDIUMllama.cpp null pointer dereference in gguf_init_from_fileEPSS 0.3%