Service crash via unchecked ZFP schunk pointer
Published Dec 25, 2023 · Updated Aug 2, 2024
NULL pointer dereference in C-Blosc2 before 2.9.3 allows remote attackers to crash applications during ZFP decompression. The zfp_rate_decompress function uses dparams->schunk without first checking whether the nested pointer identifies an existing chunk. A consuming application must decompress an attacker-supplied chunk with the ZFP fixed-rate codec; the direct consequence is process termination.
Summary
What happened
NULL pointer dereference in C-Blosc2 before 2.9.3 allows remote attackers to crash applications during ZFP decompression. The zfp_rate_decompress function uses dparams->schunk without first checking whether the nested pointer identifies an existing chunk. A consuming application must decompress an attacker-supplied chunk with the ZFP fixed-rate codec; the direct consequence is process termination.
The record
- CVE
- CVE-2023-37188
- Published
- Dec 25, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 25, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- C-Blosc2 ZFP decompression fuzz reproducerproof of concept · 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