# CVE-2019-1010305: Memory corruption in libmspack > A buffer overflow in libmspack allows information disclosure when a user opens a specially crafted CHM file. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 15 Jul 2019 - **Updated:** 5 Aug 2024 - **Also known as:** ALPINE-CVE-2019-1010305, ALSA-2020:1686, DEBIAN-CVE-2019-1010305, DLA-1895-1, DLA-2805-1, GHSA-w7hv-jwj8-qh4r, MGASA-2019-0248, RHSA-2020:1686, RHSA-2020:3848, RLSA-2020:1686, SUSE-SU-2020:1493-1, UBUNTU-CVE-2019-1010305, USN-4066-1, USN-4066-2, openSUSE-SU-2020:0746-1 ## What is CVE-2019-1010305? CVE-2019-1010305 is a medium-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 15 Jul 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2019-1010305? It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libmspack` | AlmaLinux:8 | All versions | 0.7-0.3.alpha.el8.4 | | `libmspack-devel` | AlmaLinux:8 | All versions | 0.7-0.3.alpha.el8.4 | | `libmspack` | Red Hat:enterprise_linux:7::client | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack` | Red Hat:enterprise_linux:7::server | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.5-0.8.alpha.el7 | | `libmspack` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.7-0.3.alpha.el8.4 | | `libmspack-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.7-0.3.alpha.el8.4 | | `libmspack-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.7-0.3.alpha.el8.4 | | `libmspack` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7-0.3.alpha.el8.4 | | `libmspack-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7-0.3.alpha.el8.4 | | `libmspack-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7-0.3.alpha.el8.4 | | `libmspack-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:0.7-0.3.alpha.el8.4 | | `libmspack` | Rocky Linux:8 | All versions | 0:0.7-0.3.alpha.el8.4 | | `libmspack` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 0.6-3.8.19 | | `libmspack` | openSUSE:Leap 15.1 | All versions | 0.6-lp151.4.3.1 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Kyzer Libmspack. ## How do I fix CVE-2019-1010305? Apply the vendor's patch. ## Is CVE-2019-1010305 being exploited? There is no known exploitation of CVE-2019-1010305 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-1010305 and fix it if it is affected. What it is: CVE-2019-1010305 is a medium-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 15 Jul 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2019-1010305 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-1010305/ (Markdown: https://insights.sbomify.com/CVE-2019-1010305/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1010305 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1010305 - OSV: https://osv.dev/vulnerability/CVE-2019-1010305 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1010305/ Summaries are generated and may contain mistakes; the official description above is the record.