HDF5 1.8.20 H5Olink.c H5O_link_decode memcpy memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in HDF5 1.8.20. It has been rated as critical. This impacts the function H5O_link_decode of the file H5Olink.c. The manipulation of the argument memcpy as part of Parameter leads to memory corruption.
This vulnerability is listed as CVE-2018-13869. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in HDF5 1.8.20 (Database Software) and classified as critical. This issue affects the function H5O_link_decode of the file H5Olink.c. The manipulation of the argument memcpy as part of a Parameter leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in the HDF HDF5 1.8.20 library. There is a memcpy parameter overlap in the function H5O_link_decode in H5Olink.c.
The bug was discovered 07/11/2018. The weakness was presented 07/10/2018 (Website). It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2018-13869 since 07/10/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-121160, VDB-121161, VDB-121162 and VDB-121164 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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: 🔍
Timeline
07/10/2018 🔍07/10/2018 🔍
07/10/2018 🔍
07/11/2018 🔍
07/11/2018 🔍
03/02/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-13869 (🔍)
GCVE (CVE): GCVE-0-2018-13869
GCVE (VulDB): GCVE-100-121163
See also: 🔍
Entry
Created: 07/11/2018 11:07Updated: 03/02/2020 08:24
Changes: 07/11/2018 11:07 (59), 03/02/2020 08:24 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.