# CVE-2019-11769: Information disclosure in n/a

> Local attackers can intercept administrative credentials from TeamViewer process memory to elevate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** No
- **Published:** 11 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-phx3-9j7m-hxph

## What is CVE-2019-11769?

CVE-2019-11769 is a high-severity vulnerability in n/a, published on 11 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in TeamViewer 14.2.2558. Updating the product as a non-administrative user requires entering administrative credentials into the GUI. Subsequently, these credentials are processed in Teamviewer.exe, which allows any application running in the same non-administrative user context to intercept them in cleartext within process memory. By using this technique, a local attacker is able to obtain administrative credentials in order to elevate privileges. This vulnerability can be exploited by injecting code into Teamviewer.exe which intercepts calls to GetWindowTextW and logs the processed credentials.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Teamviewer Teamviewer.

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

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

## Is CVE-2019-11769 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-18988](https://insights.sbomify.com/CVE-2019-18988/): TeamViewer Desktop Bypass Remote Login (high 7.0, exploited in the wild)
- [CVE-2018-16550](https://insights.sbomify.com/CVE-2018-16550/): Security feature bypass in n/a (critical 9.8)
- [CVE-2010-3128](https://insights.sbomify.com/CVE-2010-3128/): Path traversal in n/a (critical 9.3)
- [CVE-2020-13699](https://insights.sbomify.com/CVE-2020-13699/): Command injection in n/a (high 8.8)
- [CVE-2018-14333](https://insights.sbomify.com/CVE-2018-14333/): Information disclosure in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11769 is a high-severity vulnerability in n/a, published on 11 Sep 2019. 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-2019-11769 in the wild and no public exploit code.

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

## Sources

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

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