ggerganov llama.cpp b3427 rpc_tensor write-what-where condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as very critical has been reported in ggerganov llama.cpp. This impacts the function rpc_tensor. Performing a manipulation results in write-what-where condition.
This vulnerability was named CVE-2024-42479. The attack may be initiated remotely. There is no available exploit.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in ggerganov llama.cpp. It has been classified as very critical. This affects the function rpc_tensor. The manipulation with an unknown input leads to a write-what-where condition vulnerability. CWE is classifying the issue as CWE-123. Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
llama.cpp provides LLM inference in C/C++. The unsafe `data` pointer member in the `rpc_tensor` structure can cause arbitrary address writing. This vulnerability is fixed in b3561.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-42479 since 08/02/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/16/2024).
Upgrading to version b3561 eliminates this vulnerability. Applying the patch b72942fac998672a79a1ae3c03b340f7e629980b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.7
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 10.0
CNA Vector (GitHub_M): 🔍
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: Write-what-where conditionCWE: CWE-123 / CWE-119
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: llama.cpp b3561
Patch: b72942fac998672a79a1ae3c03b340f7e629980b
Timeline
08/02/2024 🔍08/12/2024 🔍
08/12/2024 🔍
08/16/2024 🔍
Sources
Product: github.comAdvisory: GHSA-wcr5-566p-9cwj
Status: Confirmed
CVE: CVE-2024-42479 (🔍)
GCVE (CVE): GCVE-0-2024-42479
GCVE (VulDB): GCVE-100-274173
Entry
Created: 08/12/2024 17:54Updated: 08/16/2024 13:02
Changes: 08/12/2024 17:54 (66), 08/16/2024 13:02 (10)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.