Code execution via unchecked OSCORE configuration length
Published Jan 27, 2024 · Updated Jun 17, 2025
Stack-based buffer overflow in libcoap 4.3.4 allows local users to execute code or crash applications via a crafted OSCORE configuration. get_split_entry parses an overlong hex_aster_secret value into a fixed stack destination without enforcing its capacity. Triggering requires an application to pass attacker-controlled configuration bytes to coap_new_oscore_conf; demonstrated consequences include a crash and potential code execution.
Summary
What happened
Stack-based buffer overflow in libcoap 4.3.4 allows local users to execute code or crash applications via a crafted OSCORE configuration. get_split_entry parses an overlong hex_aster_secret value into a fixed stack destination without enforcing its capacity. Triggering requires an application to pass attacker-controlled configuration bytes to coap_new_oscore_conf; demonstrated consequences include a crash and potential code execution.
The record
- CVE
- CVE-2024-0962
- Published
- Jan 27, 2024
- Updated
- Jun 17, 2025
- Vendor
- libcoap
- Product
- libcoap
- Classifications
- CWE-787, CWE-121, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 27, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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=4.3.4
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
- Upstream stack-overflow reproducer and crash inputfunctional · 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