| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in libxls 1.4.0. The affected element is the function ole2_read_header of the file ole.c. Performing a manipulation results in memory corruption.
This vulnerability is cataloged as CVE-2018-20452. It is possible to initiate the attack remotely. There is no exploit available.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability was found in libxls 1.4.0. It has been classified as critical. This affects the function ole2_read_header of the file ole.c. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The read_MSAT_body function in ole.c in libxls 1.4.0 has an invalid free that allows attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted file, because of inconsistent memory management (new versus free) in ole2_read_header in ole.c.
The bug was discovered 12/25/2018. The weakness was shared 12/25/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-20452 since 12/25/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry VDB-128407 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: 🔍
0-Day Time: 🔍
Timeline
12/25/2018 🔍12/25/2018 🔍
12/25/2018 🔍
12/25/2018 🔍
12/26/2018 🔍
06/22/2023 🔍
Sources
Advisory: 35Status: Not defined
CVE: CVE-2018-20452 (🔍)
GCVE (CVE): GCVE-0-2018-20452
GCVE (VulDB): GCVE-100-128409
See also: 🔍
Entry
Created: 12/26/2018 09:38 PMUpdated: 06/22/2023 07:33 AM
Changes: 12/26/2018 09:38 PM (57), 04/24/2020 10:36 AM (1), 06/22/2023 07:33 AM (3)
Complete: 🔍
Cache ID: 244:8B3:40
No comments yet. Languages: en.
Please log in to comment.