CVE-2024-3203 | c-blosc2 ndlz8x8.c ndlz8_decompress heap-based overflow

Exp

A vulnerability, which was classified as critical, was found in c-blosc2 up to 2.13.2. Affected is the function ndlz8_decompress of the file /src/c-blosc2/plugins/codecs/ndlz/ndlz8x8.c. The manipulation leads to heap-based buffer overflow. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.14.3 is able to address this issue. It is recommended to upgrade the affected component. VDB-259050 is the identifier assigned to this vulnerability.

Published: 2024-04-02 Last update: 2025-04-25 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-3203 is rated High Exploit Risk (68.4/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.57%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-3203

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-3203

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-21 0.42% 0.57% +0.15%
2 2026-01-27 0.31% 0.42% +0.11%
3 2025-11-21 — 0.31% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-3203

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 3.4 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2024-3203

OS Trackers for CVE-2024-3203

vendor priority summary link
debian not yet assigned CVE-2024-3203 not yet assigned priority: Debian including 1 source packages (c-blosc2), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2024-3203
suse high CVE-2024-3203 severity important: SUSE including 3 source package names (blosc2-devel-2.14.4-1.1, libblosc2-3-2.14.4-1.1, libblosc2-3-x86-64-v3-2.14.4-1.1), 3 product×package rows across 1 product lines (openSUSE Tumbleweed): Fixed 3. https://www.suse.com/security/cve/CVE-2024-3203/
ubuntu medium CVE-2024-3203 medium priority: Ubuntu including 1 source packages (c-blosc2), 8 status rows across 8 suites (focal, jammy, mantic, noble, oracular, plucky, questing, upstream): DNE 3, needs-triage 3, ignored 2. https://ubuntu.com/security/CVE-2024-3203

Affected software / configurations for CVE-2024-3203

Vendor Product Version Raw CPE
blosc c-blosc2 <= 2.13.2 cpe:2.3:a:blosc:c-blosc2:*:*:*:*:*:*:*:*

References for CVE-2024-3203

cvelogic Threat Intelligence