CVE-2024-42479Public exploitNetwork attack vector

Unauthenticated arbitrary memory write via RPC tensor pointer

Published Aug 12, 2024 · Updated Aug 13, 2024

Write-what-where in llama.cpp before b3561 allows remote attackers to overwrite arbitrary process memory through the RPC server. rpc_server::set_tensor trusts the serialized rpc_tensor.data pointer and passes it to ggml_backend_cpu_buffer_set_tensor, where memcpy writes supplied bytes without checking that the destination lies inside the allocated backend buffer. RPC network reachability is the only gate; unauthenticated requests enable process crashes and an arbitrary-write primitive that supports code execution when paired with an address-read primitive.

CVSS severity9.8
Critical
EPSS probability2.63%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Write-what-where in llama.cpp before b3561 allows remote attackers to overwrite arbitrary process memory through the RPC server. rpc_server::set_tensor trusts the serialized rpc_tensor.data pointer and passes it to ggml_backend_cpu_buffer_set_tensor, where memcpy writes supplied bytes without checking that the destination lies inside the allocated backend buffer. RPC network reachability is the only gate; unauthenticated requests enable process crashes and an arbitrary-write primitive that supports code execution when paired with an address-read primitive.

The record

CVE
CVE-2024-42479
Published
Aug 12, 2024
Updated
Aug 13, 2024
Vendor
Georgi Gerganov
Product
llama.cpp
Classifications
CWE-123, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 12, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 13, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <b3561
  2. Affected versionversion=< b3561

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Georgi Gerganov · llama.cppversion=0 <b3561; version=< b3561

Published CVSS scores

9.8GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-123Write-what-where Condition
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo