Crash or code execution via unchecked hostname copy
Published Dec 31, 2025 · Updated Dec 31, 2025
Stack-based buffer overflow in libcoap 4.3.5 and earlier allows remote attackers to crash proxy-enabled applications via a crafted hostname. coap_resolve_address_info() copies address->length bytes into the fixed 256-byte addrstr stack buffer without first rejecting oversized hostnames. The proxy request path must be enabled; memory protections and compiler options determine whether corruption stops at a crash or permits code execution.
Summary
What happened
Stack-based buffer overflow in libcoap 4.3.5 and earlier allows remote attackers to crash proxy-enabled applications via a crafted hostname. coap_resolve_address_info() copies address->length bytes into the fixed 256-byte addrstr stack buffer without first rejecting oversized hostnames. The proxy request path must be enabled; memory protections and compiler options determine whether corruption stops at a crash or permits code execution.
The record
- CVE
- CVE-2025-34468
- Published
- Dec 31, 2025
- Updated
- Dec 31, 2025
- Vendor
- libcoap
- Product
- libcoap
- Classifications
- CWE-787, CWE-121, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 31, 2025CVE publishedPublication date reported by the CVE source.
- Dec 31, 2025Record 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 <=4.3.5
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
No public exploit references are available in this record.
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