# CVE-2019-5068: Missing authorization in Mesa 3D X11 Graphics library > An attacker can access shared memory without specific permissions in the Mesa 3D Graphics Library, leading to unauthorized data access. - **Severity:** Medium 5.1 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 5 Nov 2019 - **Updated:** 4 Aug 2024 - **Also known as:** DEBIAN-CVE-2019-5068, DLA-1993-1, GHSA-rrg9-xrw3-h9vv, SUSE-SU-2020:0111-1, SUSE-SU-2020:0111-2, SUSE-SU-2020:0132-1, SUSE-SU-2020:0145-1, SUSE-SU-2020:0146-1, SUSE-SU-2021:3117-1, UBUNTU-CVE-2019-5068, USN-4271-1, openSUSE-SU-2020:0084-1, openSUSE-SU-2024:10599-1 ## What is CVE-2019-5068? CVE-2019-5068 is a medium-severity missing authorization vulnerability in Canonical Ubuntu Linux, published on 5 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description An exploitable shared memory permissions vulnerability exists in the functionality of X11 Mesa 3D Graphics Library 19.1.2. An attacker can access the shared memory without any specific permissions to trigger this vulnerability. Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-277 (Insecure Inherited Permissions) ## Which versions are affected by CVE-2019-5068? It affects 4 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `Mesa` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 18.0.2-8.3.2 | | `Mesa-drivers` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 18.0.2-8.3.2 | | `Mesa` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 18.0.2-27.6.1 | | `Mesa-drivers` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 18.0.2-27.6.1 | | `Mesa` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 18.3.2-34.9.1 | | `Mesa-drivers` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 18.3.2-34.9.1 | | `Mesa` | SUSE:Linux Enterprise Module for Package Hub 15 SP1 | All versions | 18.3.2-34.9.1 | | `Mesa` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 11.2.1-104.9.49 | | `Mesa` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 18.0.2-8.3.2 | | `Mesa-drivers` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 18.0.2-8.3.2 | | `Mesa` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 18.3.2-14.3.2 | | `Mesa-drivers` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 18.3.2-14.3.2 | | `Mesa` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 18.0.2-8.3.2 | | `Mesa-drivers` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 18.0.2-8.3.2 | | `Mesa` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 18.3.2-14.3.2 | | `Mesa-drivers` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 18.3.2-14.3.2 | | `Mesa` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 18.0.2-8.3.2 | | `Mesa-drivers` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 18.0.2-8.3.2 | | `Mesa` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 11.2.1-104.9.49 | | `Mesa` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 18.3.2-14.3.2 | | `Mesa-drivers` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 18.3.2-14.3.2 | | `Mesa` | SUSE:Linux Enterprise Workstation Extension 12 SP4 | All versions | 18.0.2-8.3.2 | | `Mesa` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 18.3.2-14.3.2 | | `Mesa-drivers` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 18.3.2-14.3.2 | | `Mesa-drivers` | SUSE:Linux Enterprise Workstation Extension 15 | All versions | 18.0.2-27.6.1 | | `Mesa-drivers` | SUSE:Linux Enterprise Workstation Extension 15 SP1 | All versions | 18.3.2-34.9.1 | | `Mesa` | openSUSE:Leap 15.1 | All versions | 18.3.2-lp151.23.9.1 | | `Mesa-drivers` | openSUSE:Leap 15.1 | All versions | 18.3.2-lp151.23.9.1 | Products: Canonical Ubuntu Linux, Debian Debian Linux, Mesa3d Mesa, Opensuse Leap. ## How do I fix CVE-2019-5068? Apply the vendor's patch. ## Is CVE-2019-5068 being exploited? There is no known exploitation of CVE-2019-5068 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-5068 and fix it if it is affected. What it is: CVE-2019-5068 is a medium-severity missing authorization vulnerability in Canonical Ubuntu Linux, published on 5 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-5068 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-5068/ (Markdown: https://insights.sbomify.com/CVE-2019-5068/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-5068 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-5068 - OSV: https://osv.dev/vulnerability/CVE-2019-5068 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-5068/ Summaries are generated and may contain mistakes; the official description above is the record.