Service crash via malformed GGUF tensor name
Published Jul 22, 2024 · Updated Aug 2, 2024
Null pointer dereference in llama.cpp before b3427 allows attackers to crash the application by supplying a malformed GGUF model file. A failed tensor-name read leaves name.data null, but gguf_init_from_file still passes that pointer to strcmp while checking for duplicate names. A user or consuming service must load the crafted file; the demonstrated consequence is a segmentation-fault service interrupt.
Summary
What happened
Null pointer dereference in llama.cpp before b3427 allows attackers to crash the application by supplying a malformed GGUF model file. A failed tensor-name read leaves name.data null, but gguf_init_from_file still passes that pointer to strcmp while checking for duplicate names. A user or consuming service must load the crafted file; the demonstrated consequence is a segmentation-fault service interrupt.
The record
- CVE
- CVE-2024-41130
- Published
- Jul 22, 2024
- Updated
- Aug 2, 2024
- Vendor
- Georgi Gerganov
- Product
- llama.cpp
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.
- Affected versionversion=0 <b3427
- Affected versionversion=< b3427
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
- Malformed GGUF null-dereference proof of conceptproof of concept · demonstrated
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