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

> Local attackers with sufficient privileges can read sensitive chat data from memory after logout or history deletion in TeamViewer.

- **Severity:** Medium 4.3 (`CVSS:3.0/AC:L/AV:P/A:N/C:H/I:N/PR:L/S:U/UI:N`)
- **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:** 2 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rjwh-hm8r-vg38

## What is CVE-2019-19362?

CVE-2019-19362 is a medium-severity vulnerability in n/a, published on 2 Dec 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 the Chat functionality of the TeamViewer desktop application 14.3.4730 on Windows. (The vendor states that it was later fixed.) Upon login, every communication is saved within Windows main memory. When a user logs out or deletes conversation history (but does not exit the application), this data is not wiped from main memory, and therefore could be read by a local user with the same or greater privileges.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer)

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

It affects 1 product.


Products: Teamviewer Teamviewer.

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

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

## Is CVE-2019-19362 being exploited?

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

What it is: CVE-2019-19362 is a medium-severity vulnerability in n/a, published on 2 Dec 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-19362 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-19362/ (Markdown: https://insights.sbomify.com/CVE-2019-19362/index.md)
```

## Sources

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

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