# CVE-2024-42479: llama.cpp allows write-what-where in rpc_server::set_tensor

> An attacker can achieve arbitrary memory write and potential code execution via unsafe pointer handling in the RPC server tensor setting function.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2024
- **Updated:** 13 Aug 2024
- **Also known as:** GHSA-wcr5-566p-9cwj

## What is CVE-2024-42479?

CVE-2024-42479 is a critical memory corruption vulnerability in ggerganov llama.cpp, published on 12 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-787 (Out-of-bounds Write), CWE-123 (Write-what-where Condition)

## Which versions are affected by CVE-2024-42479?

It affects 1 product.


Products: Ggml Llama.cpp.

## How do I fix CVE-2024-42479?

No fix has been published for CVE-2024-42479 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-42479 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42479 exists.

## Other vulnerabilities in ggerganov llama.cpp

- [CVE-2026-34159](https://insights.sbomify.com/CVE-2026-34159/): llama.cpp: Unauthenticated RCE via GRAPH_COMPUTE buffer=0 bypass in llama.cpp RPC backend (critical 9.8)
- [CVE-2026-43629](https://insights.sbomify.com/CVE-2026-43629/): llama.cpp b4882–b9058 Buffer Overflow in KV Cache State Restore (critical 9.2)
- [CVE-2026-43631](https://insights.sbomify.com/CVE-2026-43631/): llama.cpp b7492–b9060 Use-After-Free RCE via llama-server (critical 9.2)
- [CVE-2026-43632](https://insights.sbomify.com/CVE-2026-43632/): llama.cpp b7492–b9060 Use-After-Free in Tokenization Endpoints (critical 9.2)
- [CVE-2026-21869](https://insights.sbomify.com/CVE-2026-21869/): llama.cpp has Out-of-bounds Write in llama-server (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42479 and fix it if it is affected.

What it is: CVE-2024-42479 is a critical memory corruption vulnerability in ggerganov llama.cpp, published on 12 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42479 exists.

Affected product: ggerganov llama.cpp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-42479/ (Markdown: https://insights.sbomify.com/CVE-2024-42479/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-42479
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-42479
- OSV: https://osv.dev/vulnerability/CVE-2024-42479

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-42479/
Summaries are generated and may contain mistakes; the official description above is the record.