# CVE-2019-1010238: Memory corruption in Pango > A heap-based buffer overflow in Gnome Pango allows attackers to execute arbitrary code by passing invalid UTF-8 strings to text processing functions. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Jul 2019 - **Updated:** 5 Aug 2024 - **Also known as:** ALPINE-CVE-2019-1010238, AZL-110504, DEBIAN-CVE-2019-1010238, DSA-4496-1, GHSA-wwvc-98fq-c42m, JLSEC-2026-455, MGASA-2019-0235, RHSA-2019:2571, RHSA-2019:2582, RHSA-2019:3234 ## What is CVE-2019-1010238? CVE-2019-1010238 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 19 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Gnome Pango 1.42 and later is affected by: Buffer Overflow. The impact is: The heap based buffer overflow can be used to get code execution. The component is: function name: pango_log2vis_get_embedding_levels, assignment of nchars and the loop condition. The attack vector is: Bug can be used when application pass invalid utf-8 strings to functions like pango_itemize. Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2019-1010238? It affects 13 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pango` | Red Hat:enterprise_linux:7::client | All versions | 0:1.42.4-4.el7_7 | | `pango-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.42.4-4.el7_7 | | `pango-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.42.4-4.el7_7 | | `pango-tests` | Red Hat:enterprise_linux:7::client | All versions | 0:1.42.4-4.el7_7 | | `pango` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.42.4-4.el7_7 | | `pango-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.42.4-4.el7_7 | | `pango-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.42.4-4.el7_7 | | `pango-tests` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.42.4-4.el7_7 | | `pango` | Red Hat:enterprise_linux:7::server | All versions | 0:1.42.4-4.el7_7 | | `pango-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.42.4-4.el7_7 | | `pango-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.42.4-4.el7_7 | | `pango-tests` | Red Hat:enterprise_linux:7::server | All versions | 0:1.42.4-4.el7_7 | | `pango` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.42.4-4.el7_7 | | `pango-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.42.4-4.el7_7 | | `pango-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.42.4-4.el7_7 | | `pango-tests` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.42.4-4.el7_7 | | `pango` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.42.4-5.el8_0 | | `pango-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.42.4-5.el8_0 | | `pango-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.42.4-5.el8_0 | | `pango-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.42.4-5.el8_0 | | `pango-tests-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.42.4-5.el8_0 | | `pango` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:1.42.4-3.el7_6 | | `pango-debuginfo` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:1.42.4-3.el7_6 | | `pango-devel` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:1.42.4-3.el7_6 | | `pango-tests` | Red Hat:rhel_eus:7.6::computenode | All versions | 0:1.42.4-3.el7_6 | | `pango` | Red Hat:rhel_eus:7.6::server | All versions | 0:1.42.4-3.el7_6 | | `pango-debuginfo` | Red Hat:rhel_eus:7.6::server | All versions | 0:1.42.4-3.el7_6 | | `pango-devel` | Red Hat:rhel_eus:7.6::server | All versions | 0:1.42.4-3.el7_6 | | `pango-tests` | Red Hat:rhel_eus:7.6::server | All versions | 0:1.42.4-3.el7_6 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora, Gnome Pango, Oracle Sd-Wan Edge, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation, Redhat Openshift Container Platform. ## How do I fix CVE-2019-1010238? Apply the vendor's patch. ## Is CVE-2019-1010238 being exploited? There is no known exploitation of CVE-2019-1010238 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-1010238 and fix it if it is affected. What it is: CVE-2019-1010238 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 19 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-1010238 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-1010238/ (Markdown: https://insights.sbomify.com/CVE-2019-1010238/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1010238 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1010238 - OSV: https://osv.dev/vulnerability/CVE-2019-1010238 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1010238/ Summaries are generated and may contain mistakes; the official description above is the record.