# CVE-2024-12363: Insufficient permissions in the TeamViewer Patch & Asset Management component

> A local authenticated user can delete arbitrary files due to insufficient permissions in TeamViewer Patch & Asset Management.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 Dec 2024
- **Updated:** 11 Dec 2024
- **Also known as:** GHSA-wrjq-3whp-rqcq

## What is CVE-2024-12363?

CVE-2024-12363 is a high-severity missing authorization vulnerability in TeamViewer Patch & Asset Management, published on 11 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient permissions in the TeamViewer Patch & Asset Management component prior to version 24.12 on Windows allows a local authenticated user to delete arbitrary files. TeamViewer Patch & Asset Management is part of TeamViewer Remote Management.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2024-12363 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-12363 is a high-severity missing authorization vulnerability in TeamViewer Patch & Asset Management, published on 11 Dec 2024. 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-2024-12363 in the wild and no public exploit code.

Affected product: TeamViewer Patch & Asset Management. 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-12363/ (Markdown: https://insights.sbomify.com/CVE-2024-12363/index.md)
```

## Sources

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

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