# CVE-2019-2201: Memory corruption in Android > An out-of-bounds write in Android's NEON assembly allows remote code execution in unprivileged processes via user interaction. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **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:** 13 Nov 2019 - **Updated:** 4 Aug 2024 - **Also known as:** ALPINE-CVE-2019-2201, CLEANSTART-2026-ET03360, DEBIAN-CVE-2019-2201, DLA-3037-1, GHSA-x9wg-q72x-x5w7, MGASA-2019-0329, SUSE-SU-2019:2971-1, SUSE-SU-2019:2971-2, SUSE-SU-2019:2972-1, UBUNTU-CVE-2019-2201, openSUSE-SU-2019:2529-1, openSUSE-SU-2019:2530-1 ## What is CVE-2019-2201? CVE-2019-2201 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 13 Nov 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 In generate_jsimd_ycc_rgb_convert_neon of jsimd_arm64_neon.S, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution in an unprivileged process with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-120551338 Weakness: CWE-787 (Out-of-bounds Write) ## Which versions are affected by CVE-2019-2201? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libjpeg-turbo` | SUSE:Enterprise Storage 5 | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Enterprise Storage 5 | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:HPE Helion OpenStack 8 | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:HPE Helion OpenStack 8 | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 1.5.3-5.12.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 1.5.3-5.12.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 1.5.3-5.12.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 1.5.3-5.12.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 SP2 | All versions | 1.5.3-5.12.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Module for Basesystem 15 SP2 | All versions | 1.5.3-5.12.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Desktop Applications 15 | All versions | 1.5.3-5.12.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP1 | All versions | 1.5.3-5.12.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP2 | All versions | 1.5.3-5.12.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Package Hub 15 | All versions | 1.5.3-5.12.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Package Hub 15 SP1 | All versions | 1.5.3-5.12.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Module for Package Hub 15 SP2 | All versions | 1.5.3-5.12.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.5.3-31.19.1 | | `libjpeg-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.5.3-31.19.1 | | `libjpeg62-turbo` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.5.3-31.19.1 | Products: Canonical Ubuntu Linux, Google Android. ## How do I fix CVE-2019-2201? Apply the vendor's patch. ## Is CVE-2019-2201 being exploited? There is no known exploitation of CVE-2019-2201 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-2201 and fix it if it is affected. What it is: CVE-2019-2201 is a high-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 13 Nov 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-2201 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-2201/ (Markdown: https://insights.sbomify.com/CVE-2019-2201/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-2201 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-2201 - OSV: https://osv.dev/vulnerability/CVE-2019-2201 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-2201/ Summaries are generated and may contain mistakes; the official description above is the record.