# CVE-2018-15127: Memory corruption in LibVNC

> A heap out-of-bound write in LibVNC's file transfer extension allows remote attackers to execute arbitrary code.

- **Severity:** Critical 9.8 (`CVSS:3.0/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 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-15127, GHSA-2pgv-ghf3-xj9q, RHSA-2019:0059, UBUNTU-CVE-2018-15127

## What is CVE-2018-15127?

CVE-2018-15127 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 19 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LibVNC before commit 502821828ed00b4a2c4bef90683d0fd88ce495de contains heap out-of-bound write vulnerability in server code of file transfer extension that can result remote code execution

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 9 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libvncserver` | Red Hat:enterprise_linux:7::client | All versions | 0:0.9.9-13.el7_6 |
| `libvncserver-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:0.9.9-13.el7_6 |
| `libvncserver-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:0.9.9-13.el7_6 |
| `libvncserver` | Red Hat:enterprise_linux:7::server | All versions | 0:0.9.9-13.el7_6 |
| `libvncserver-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:0.9.9-13.el7_6 |
| `libvncserver-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:0.9.9-13.el7_6 |
| `libvncserver` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.9.9-13.el7_6 |
| `libvncserver-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.9.9-13.el7_6 |
| `libvncserver-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:0.9.9-13.el7_6 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Libvnc Project Libvncserver, 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-15127?

Apply the vendor's patch.

## Is CVE-2018-15127 being exploited?

There is no known exploitation of CVE-2018-15127 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-2018-15127 and fix it if it is affected.

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

## Sources

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

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