# CVE-2024-6053: Improper access control in the clipboard synchronization feature

> An attacker can unintentionally access clipboard data shared during a meeting due to improper access control in TeamViewer clients.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Aug 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-mpvq-wpj3-wjgw

## What is CVE-2024-6053?

CVE-2024-6053 is a medium-severity vulnerability in TeamViewer Meeting, published on 28 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper access control in the clipboard synchronization feature in TeamViewer Full Client prior version 15.57 and TeamViewer Meeting prior version 15.55.3 can lead to unintentional sharing of the clipboard with the current presenter of a meeting.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-6053?

It affects 2 products.


Products: Teamviewer Meeting, Teamviewer Teamviewer.

## How do I fix CVE-2024-6053?

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

## Is CVE-2024-6053 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6053 and fix it if it is affected.

What it is: CVE-2024-6053 is a medium-severity vulnerability in TeamViewer Meeting, published on 28 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-6053 in the wild and no public exploit code.

Affected product: TeamViewer Meeting. 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-2024-6053/ (Markdown: https://insights.sbomify.com/CVE-2024-6053/index.md)
```

## Sources

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

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