HDF5 1.10.2 HDF File H5Dchunk.c H5D__chunk_init divide by zero
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in HDF5 1.10.2. It has been classified as problematic. This impacts the function H5D__chunk_init of the file H5Dchunk.c of the component HDF File Handler. This manipulation causes divide by zero.
This vulnerability is handled as CVE-2018-15672. There is not any exploit available.
Details
A vulnerability classified as problematic was found in HDF5 1.10.2 (Database Software). Affected by this vulnerability is the function H5D__chunk_init of the file H5Dchunk.c of the component HDF File Handler. The manipulation with an unknown input leads to a divide by zero vulnerability. The CWE definition for the vulnerability is CWE-369. The product divides a value by zero. As an impact it is known to affect availability. The summary by CVE is:
An issue was discovered in the HDF HDF5 1.10.2 library. A SIGFPE is raised in the function H5D__chunk_init() of H5Dchunk.c during an attempted parse of a crafted HDF file, because of incorrect protection against division by zero.
The bug was discovered 08/18/2018. The weakness was released 08/21/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-15672 since 08/21/2018. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entry connected to this vulnerability is available at VDB-123120. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Divide by zeroCWE: CWE-369 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/18/2018 🔍08/21/2018 🔍
08/21/2018 🔍
08/22/2018 🔍
03/17/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-15672 (🔍)
GCVE (CVE): GCVE-0-2018-15672
GCVE (VulDB): GCVE-100-123121
See also: 🔍
Entry
Created: 08/22/2018 08:17Updated: 03/17/2020 13:16
Changes: 08/22/2018 08:17 (42), 03/17/2020 13:16 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.