# CVE-2019-8275: Null dereference in UltraVNC

> Remote attackers can access out-of-bound data or cause denial of service in UltraVNC server due to improper null termination.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** No
- **Published:** 9 Mar 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hhw7-p92g-vp7v

## What is CVE-2019-8275?

CVE-2019-8275 is a critical vulnerability in Kaspersky Lab UltraVNC, published on 9 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

UltraVNC revision 1211 has multiple improper null termination vulnerabilities in VNC server code, which result in out-of-bound data being accessed by remote users. This attack appears to be exploitable via network connectivity. These vulnerabilities have been fixed in revision 1212.

Weakness: CWE-170 (Improper Null Termination)

## Which versions are affected by CVE-2019-8275?

It affects 4 products.


Products: Siemens Sinumerik Access Mymachine\/P2p, Siemens Sinumerik Pcu Base Win10 Software\/Ipc, Siemens Sinumerik Pcu Base Win7 Software\/Ipc, Uvnc Ultravnc.

## How do I fix CVE-2019-8275?

No fix has been published for CVE-2019-8275 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-8275 being exploited?

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

## Other vulnerabilities in Kaspersky Lab UltraVNC

- [CVE-2019-8268](https://insights.sbomify.com/CVE-2019-8268/): Memory corruption in UltraVNC (critical 9.8)
- [CVE-2019-8271](https://insights.sbomify.com/CVE-2019-8271/): Memory corruption in UltraVNC (critical 9.8)
- [CVE-2019-8272](https://insights.sbomify.com/CVE-2019-8272/): Integer overflow in UltraVNC (critical 9.8)
- [CVE-2019-8273](https://insights.sbomify.com/CVE-2019-8273/): Memory corruption in UltraVNC (critical 9.8)
- [CVE-2019-8274](https://insights.sbomify.com/CVE-2019-8274/): Memory corruption in UltraVNC (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8275 and fix it if it is affected.

What it is: CVE-2019-8275 is a critical vulnerability in Kaspersky Lab UltraVNC, published on 9 Mar 2019. 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-2019-8275 in the wild and no public exploit code.

Affected product: Kaspersky Lab UltraVNC. 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-8275/ (Markdown: https://insights.sbomify.com/CVE-2019-8275/index.md)
```

## Sources

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

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