# CVE-2018-1000199: Memory corruption in n/a

> Local attackers with ptrace access can trigger memory corruption in the Linux Kernel, leading to crashes or potential code execution.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1000199, GHSA-5qx2-85hg-v5cr, SUSE-SU-2018:1223-1, SUSE-SU-2018:1225-1, SUSE-SU-2018:1238-1, SUSE-SU-2018:1239-1, SUSE-SU-2018:1246-1, SUSE-SU-2018:1249-1, SUSE-SU-2018:1258-1, SUSE-SU-2018:1508-1, SUSE-SU-2018:1525-1, SUSE-SU-2018:1550-1, SUSE-SU-2018:1551-1, UBUNTU-CVE-2018-1000199

## What is CVE-2018-1000199?

CVE-2018-1000199 is a medium-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 24 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Linux Kernel version 3.18 contains a dangerous feature vulnerability in modify_user_hw_breakpoint() that can result in crash and possibly memory corruption. This attack appear to be exploitable via local code execution and the ability to use ptrace. This vulnerability appears to have been fixed in git commit f67b15037a7a50c57f72e69a6d59941ad90a0f0f.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2018-1000199?

It affects 10 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kgraft-patch-SLE12-SP3_Update_10` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 2-2.2 |
| `kgraft-patch-SLE12-SP3_Update_11` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 2-2.2 |
| `kgraft-patch-SLE12-SP3_Update_8` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 3-2.2 |
| `kgraft-patch-SLE12-SP3_Update_9` | SUSE:Linux Enterprise Live Patching 12 SP3 | All versions | 3-2.2 |
| `kgraft-patch-SLE12-SP1_Update_27` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 2-2.1 |
| `kgraft-patch-SLE12-SP2_Update_18` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 3-2.1 |
| `kgraft-patch-SLE12-SP2_Update_19` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 3-2.1 |
| `kgraft-patch-SLE12-SP2_Update_20` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 2-2.1 |
| `kgraft-patch-SLE12-SP2_Update_21` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 2-2.1 |
| `kgraft-patch-SLE12-SP2_Update_22` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 2-2.1 |
| `kgraft-patch-SLE12_Update_34` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 2-2.1 |
| `kgraft-patch-SLE12-SP1_Update_27` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 2-2.1 |
| `kgraft-patch-SLE12-SP2_Update_18` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 3-2.1 |
| `kgraft-patch-SLE12-SP2_Update_19` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 3-2.1 |
| `kgraft-patch-SLE12-SP2_Update_20` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2-2.1 |
| `kgraft-patch-SLE12-SP2_Update_21` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2-2.1 |
| `kgraft-patch-SLE12-SP2_Update_22` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2-2.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Linux kernel, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Server Tus, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2018-1000199?

Apply the vendor's patch.

## Is CVE-2018-1000199 being exploited?

There is no known exploitation of CVE-2018-1000199 in the wild and no public exploit code.

Public exploit code:

- https://github.com/dsfau/CVE-2018-1000199 (github_poc): https://github.com/dsfau/CVE-2018-1000199

## 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-2018-1000199 and fix it if it is affected.

What it is: CVE-2018-1000199 is a medium-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 24 May 2018. 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-2018-1000199 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-2018-1000199/ (Markdown: https://insights.sbomify.com/CVE-2018-1000199/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1000199
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1000199
- OSV: https://osv.dev/vulnerability/CVE-2018-1000199

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1000199/
Summaries are generated and may contain mistakes; the official description above is the record.
