libmspack 0.9.1alpha libmspack/mspack/chmd.c chmd_read_headers CHM File memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in libmspack 0.9.1alpha. This vulnerability affects the function chmd_read_headers of the file libmspack/mspack/chmd.c. The manipulation as part of CHM File results in memory corruption.
This vulnerability is cataloged as CVE-2019-1010305. The attack must be initiated from a local position. There is no exploit available.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability classified as critical has been found in libmspack 0.9.1alpha. Affected is the function chmd_read_headers of the file libmspack/mspack/chmd.c. The manipulation as part of a CHM File 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. CVE summarizes:
libmspack 0.9.1alpha is affected by: Buffer Overflow. The impact is: Information Disclosure. The component is: function chmd_read_headers() in libmspack(file libmspack/mspack/chmd.c). The attack vector is: the victim must open a specially crafted chm file. The fixed version is: after commit 2f084136cfe0d05e5bf5703f3e83c6d955234b4d.
The weakness was shared 07/15/2019. This vulnerability is traded as CVE-2019-1010305 since 03/20/2019. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 240049 (TencentOS Server 3: libmspack (TSSA-2022:0058)), which helps to determine the existence of the flaw in a target environment.
Applying the patch 2f084136cfe0d05e5bf5703f3e83c6d955234b4d is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at Tenable (240049). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Partially
Local: Yes
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 |
Nessus ID: 240049
Nessus Name: TencentOS Server 3: libmspack (TSSA-2022:0058)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 2f084136cfe0d05e5bf5703f3e83c6d955234b4d
Timeline
03/20/2019 🔍07/15/2019 🔍
07/16/2019 🔍
06/17/2025 🔍
Sources
Advisory: 2f084136cfe0d05e5bf5703f3e83c6d955234b4dStatus: Confirmed
CVE: CVE-2019-1010305 (🔍)
GCVE (CVE): GCVE-0-2019-1010305
GCVE (VulDB): GCVE-100-137844
Entry
Created: 07/16/2019 09:34Updated: 06/17/2025 15:08
Changes: 07/16/2019 09:34 (38), 12/02/2019 12:31 (17), 10/26/2023 13:48 (6), 10/26/2023 13:54 (1), 06/17/2025 15:08 (18)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.