# CVE-2019-1010180: Memory corruption in gdb > An out-of-bounds memory access in GNU gdb allows attackers to cause denial of service, disclose memory, or potentially execute code by opening a malicious ELF file. - **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:** 24 Jul 2019 - **Updated:** 14 Oct 2026 - **Also known as:** CLSA-2025-1764771100, CLSA-2026-1776693427, CLSA-2026-1777308938, CLSA-2026-1777446434, DEBIAN-CVE-2019-1010180, GHSA-rcgh-h6mp-4g9q, MGASA-2020-0239, OESA-2022-2002, RHSA-2020:1635, SUSE-SU-2019:14207-1, SUSE-SU-2019:2902-1, SUSE-SU-2019:2913-1, SUSE-SU-2019:2914-1, SUSE-SU-2019:2916-1, UBUNTU-CVE-2019-1010180, openSUSE-SU-2019:2493-1, openSUSE-SU-2019:2494-1, openSUSE-SU-2024:10778-1 ## What is CVE-2019-1010180? CVE-2019-1010180 is a high-severity memory corruption vulnerability in Opensuse Leap, published on 24 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 GNU gdb All versions is affected by: Buffer Overflow - Out of bound memory access. The impact is: Deny of Service, Memory Disclosure, and Possible Code Execution. The component is: The main gdb module. The attack vector is: Open an ELF for debugging. The fixed version is: Not fixed yet. Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2019-1010180? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `gdb` | Red Hat:enterprise_linux:8::appstream | All versions | 0:8.2-11.el8 | | `gdb-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:8.2-11.el8 | | `gdb-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:8.2-11.el8 | | `gdb-doc` | Red Hat:enterprise_linux:8::appstream | All versions | 0:8.2-11.el8 | | `gdb-gdbserver` | Red Hat:enterprise_linux:8::appstream | All versions | 0:8.2-11.el8 | | `gdb-headless` | Red Hat:enterprise_linux:8::appstream | All versions | 0:8.2-11.el8 | | `gdb` | SUSE:Enterprise Storage 5 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:HPE Helion OpenStack 8 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Desktop 12 SP4 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Module for Development Tools 15 | All versions | 8.3.1-3.13.1 | | `gdb` | SUSE:Linux Enterprise Module for Development Tools 15 SP1 | All versions | 8.3.1-8.8.1 | | `gdb` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 7.5.1-0.9.6.1 | | `gdb` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 8.3.1-1.12.1 | | `gdb` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 8.3.1-1.12.1 | | `gdb` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 8.3.1-1.12.1 | | `gdb` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 8.3.1-1.12.1 | | `gdb` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 8.3.1-1.12.1 | | `gdb` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:OpenStack Cloud 7 | All versions | 8.3.1-1.12.1 | | `gdb` | SUSE:OpenStack Cloud 8 | All versions | 8.3.1-2.14.1 | | `gdb` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 8.3.1-2.14.1 | | `gdb` | openSUSE:Leap 15.0 | All versions | 8.3.1-lp150.2.10.1 | | `gdb` | openSUSE:Leap 15.1 | All versions | 8.3.1-lp151.4.3.1 | | `gdb` | openSUSE:Tumbleweed | All versions | 10.1-11.2 | Products: Gnu Gdb, Opensuse Leap. ## How do I fix CVE-2019-1010180? No fix published yet. ## Is CVE-2019-1010180 being exploited? There is no known exploitation of CVE-2019-1010180 in the wild and no public exploit code. ## Other vulnerabilities in Opensuse Leap - [CVE-2005-1705](https://insights.sbomify.com/CVE-2005-1705/): Code injection in n/a (high 7.2) - [CVE-2011-4355](https://insights.sbomify.com/CVE-2011-4355/): Privilege escalation in n/a (medium 6.9) - [CVE-2023-39128](https://insights.sbomify.com/CVE-2023-39128/): Memory corruption in n/a (medium 5.5) - [CVE-2023-39129](https://insights.sbomify.com/CVE-2023-39129/): Use after free in n/a (medium 5.5) - [CVE-2023-39130](https://insights.sbomify.com/CVE-2023-39130/): Memory corruption in n/a (medium 5.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-1010180 and fix it if it is affected. What it is: CVE-2019-1010180 is a high-severity memory corruption vulnerability in Opensuse Leap, published on 24 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-1010180 in the wild and no public exploit code. Affected product: Opensuse Leap. 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-1010180/ (Markdown: https://insights.sbomify.com/CVE-2019-1010180/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1010180 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1010180 - OSV: https://osv.dev/vulnerability/CVE-2019-1010180 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-1010180/ Summaries are generated and may contain mistakes; the official description above is the record.