# CVE-2019-15683: Memory corruption in TurboVNC

> An authenticated remote attacker can exploit a stack buffer overflow in TurboVNC server to execute arbitrary code.

- **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:** 29 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g26v-2w7v-m2qp

## What is CVE-2019-15683?

CVE-2019-15683 is a critical memory corruption vulnerability in Kaspersky TurboVNC, published on 29 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TurboVNC server code contains stack buffer overflow vulnerability in commit prior to cea98166008301e614e0d36776bf9435a536136e. This could possibly result into remote code execution, since stack frame is not protected with stack canary. This attack appear to be exploitable via network connectivity. To exploit this vulnerability authorization on server is required. These issues have been fixed in commit cea98166008301e614e0d36776bf9435a536136e.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Turbovnc Turbovnc.

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

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

## Is CVE-2019-15683 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15683 is a critical memory corruption vulnerability in Kaspersky TurboVNC, published on 29 Oct 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-15683 in the wild and no public exploit code.

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

## Sources

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

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