CVE-2024-0962 is a stack-based buffer overflow (CWE-787) in get_split_entry() in the OSCORE configuration parser of libcoap 4.3.4: crafted configuration text overruns a stack buffer. NVD scores it 7.8 as a local flaw; VulDB scores it 6.3. The fix shipped in libcoap 4.3.5, and Debian patched trixie in 4.3.4-1.1+deb13u1.
Vulnerability summary
CVSS base score
7.8
High severity
EPSS score (FIRST)
0.8%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2024-0962 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| libcoap | cpe:2.3:a:libcoap:libcoap:4.3.4:*:*:*:*:*:*:* | 4.3.4 (NVD CPE); vulnerable code introduced in 4.3.2-rc1 and fixed in 4.3.5-rc1 (Debian security tracker); fixed release 4.3.5 |
| Debian libcoap3 | pkg:deb/debian/libcoap3 | trixie fixed in 4.3.4-1.1+deb13u1; unstable fixed in 4.3.5-1; bookworm 4.3.1-1 not affected (Debian security tracker) |
What does this mean for affected devices?
NVD carries VulDB's description: a flaw in "the function get_split_entry of the file src/coap_oscore.c of the component Configuration File Handler" of libcoap 4.3.4 "leads to stack-based buffer overflow." NVD's Primary score is 7.8, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, with CWE-787. VulDB, the CNA, scores it 6.3 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L), lists CWE-121 and says "the attack may be launched remotely". NVD's CPE names only 4.3.4. The record was published on 2024-01-27 (NVD).
Is it local or remote?
The reporter filed it as a local attack. Issue 1310 says the overflow "occurs in the handling of an input file in coap_new_oscore_conf() function" and gives a fuzzing harness that passes file contents to that function. coap_new_oscore_conf() parses the OSCORE configuration text that an application hands to libcoap, so the input is reachable only where the configuration comes from somewhere an attacker can write. That fits NVD's local vector better than VulDB's network vector. The fix, pull request 1311, is titled "coap_oscore.c: Fix parsing OSCORE configuration information" and was merged on 2024-01-26.
Which versions are affected?
More than NVD's CPE suggests. The Debian security tracker records that the vulnerable code was introduced in 4.3.2-rc1 and fixed in 4.3.5-rc1, which matches the libcoap ChangeLog: 4.3.2 (2023-07-13) added OSCORE support (RFC 8613) and 4.3.5 is dated 2024-07-08. A scanner that matches only the 4.3.4 CPE will miss 4.3.2 and 4.3.3 builds with OSCORE. Debian fixed trixie in 4.3.4-1.1+deb13u1 and unstable in 4.3.5-1; bookworm's 4.3.1-1 does not contain the code.
What should device makers do?
Find the libcoap version in each image with a firmware SBOM and move to 4.3.5 or later, or a vendor or distro build that carries the fix. If the product does not use OSCORE, building libcoap without it removes the parser. If it does, keep the OSCORE configuration file read-only and owned by the service. Our CoAP security guide explains where OSCORE fits, and the memory corruption fix guide covers bounded parsing. libcoap also had CVE-2025-34468, a stack overflow in hostname resolution; CVE-2019-20791 is a similar unchecked copy in OpenThread.
CVE-2024-0962 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00757, the 55.8th percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: libcoap 4.3.4 get_split_entry in src/coap_oscore.c (Configuration File Handler), stack-based buffer overflow; [email protected] Primary CVSS 3.1 7.8 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-787; [email protected] 6.3 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L, CWE-121; CPE libcoap 4.3.4; published 2024-01-27. — NVD
- Issue 1310 (opened 2024-01-25): stack-buffer-overflow, CWE-121, attack type Local; overflow occurs in the handling of an input file in coap_new_oscore_conf(); fuzzing harness passes file data to coap_new_oscore_conf(). — libcoap on GitHub
- Pull request 1311 "coap_oscore.c: Fix parsing OSCORE configuration information", fixes #1310, merged 2024-01-26. — libcoap on GitHub
- Debian: introduced in v4.3.2-rc1, fixed in v4.3.5-rc1; libcoap3 trixie fixed 4.3.4-1.1+deb13u1, unstable 4.3.5-1, bookworm 4.3.1-1 not affected (vulnerable code not present); bug 1061704. — Debian security tracker
- libcoap ChangeLog: 4.3.2 (2023-07-13) adds support for RFC8613 (OSCORE); 4.3.5 dated 2024-07-08. — libcoap ChangeLog
- Not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
- EPSS 0.00757, percentile 0.55799, dataset 2026-11-17, read 2026-11-18. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which libcoap version fixes CVE-2024-0962?
libcoap 4.3.5; Debian traces the fix to 4.3.5-rc1. Debian also patched trixie in 4.3.4-1.1+deb13u1 (per the Debian security tracker and the libcoap ChangeLog).
Are libcoap versions other than 4.3.4 affected by CVE-2024-0962?
NVD lists only 4.3.4, but Debian records that the vulnerable code was introduced in 4.3.2-rc1, the release line that added OSCORE, so 4.3.2 and 4.3.3 builds with OSCORE need checking too (per NVD, the Debian security tracker and the libcoap ChangeLog).
Can CVE-2024-0962 be exploited over the network?
The overflow is in parsing OSCORE configuration text passed to coap_new_oscore_conf(), and the reporter filed it as a local attack. NVD scores it with a local vector (7.8); VulDB says it may be launched remotely and scores it 6.3 (per NVD and libcoap issue 1310).
Is CVE-2024-0962 exploited in the wild?
It is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00757, the 55.8th percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?