Remote server crash via block-wise PUT handling
Published Oct 9, 2024 · Updated Oct 10, 2024
NULL pointer dereference in libcoap 4.3.5-rc2 and earlier allows remote attackers to crash CoAP servers via block-wise PUT requests. The coap_handle_request_put_block function reads through an invalid near-null pointer while processing a PUT request that uses block-wise transfer. A reachable server with block-wise PUT handling exposed must process a triggering request sequence; the published reproduction required hours of fuzzing and caused a process crash.
Summary
What happened
NULL pointer dereference in libcoap 4.3.5-rc2 and earlier allows remote attackers to crash CoAP servers via block-wise PUT requests. The coap_handle_request_put_block function reads through an invalid near-null pointer while processing a PUT request that uses block-wise transfer. A reachable server with block-wise PUT handling exposed must process a triggering request sequence; the published reproduction required hours of fuzzing and caused a process crash.
The record
- CVE
- CVE-2024-46304
- Published
- Oct 9, 2024
- Updated
- Oct 10, 2024
- Vendor
- libcoap
- Product
- libcoap
- Classifications
- CWE-120, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 9, 2024CVE publishedPublication date reported by the CVE source.
- Oct 10, 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=4.3.5-rc2
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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