dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-12363

HIGH · 7.1 CVSS v3.1 Published 2024-12-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A local authenticated Windows user can exploit insufficient permission checks in the TeamViewer Patch & Asset Management component to delete arbitrary files on the system, representing a local privilege escalation vulnerability.

MitigationUpgrade TeamViewer Remote Management to version 24.12 or later on Windows systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify TeamViewer Remote Management is installed
    Open Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*TeamViewer*"}' in PowerShell to find TeamViewer-related entries.
    Affected if TeamViewer Remote Management or TeamViewer Patch & Asset Management appears in the installed programs list.
  2. Identify the installed version of TeamViewer Remote Management
    In Programs and Features, locate the TeamViewer Remote Management entry and note the version number displayed in the Version column. Alternatively, check the registry key HKLM:\SOFTWARE\TeamViewer for a Version or VersionId entry.
    Affected if A version number is displayed for TeamViewer Remote Management (the specific version format may vary by installation method).
  3. Compare your version to the fixed release
    Compare the installed version number to version 24.12. Review the full version string (e.g., 24.11.x, 24.10.x, etc.) and determine if it is earlier than 24.12.
    Affected if The installed version is lower than 24.12 (for example, 24.11.x, 24.10.x, or earlier major versions).
  4. Confirm the Patch & Asset Management component is present
    Check if the Patch & Asset Management functionality is available or enabled within the TeamViewer Remote Management console or client interface. This component is required for the vulnerability to be exploitable.
    Affected if The Patch & Asset Management module is present and accessible in the TeamViewer Remote Management installation.

You are affected if TeamViewer Remote Management with the Patch & Asset Management component is installed on Windows at a version lower than 24.12.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade TeamViewer Remote Management to version 24.12 or later on Windows systems.

Recommended fix High confidence

TeamViewer Remote Management version 24.12 or later

  1. Verify current version of TeamViewer Remote Management (Patch & Asset Management component) via the TeamViewer Management Console or installed software
  2. Navigate to the TeamViewer Remote Management download page or Management Console
  3. Download and install TeamViewer Remote Management version 24.12 or later
  4. Verify the patch was applied successfully by checking the software version post-installation
  5. Confirm that the Patch & Asset Management component now runs with corrected file permissions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12363 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12363 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data