CVE-2024-7479
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 · uneditedImproper verification of cryptographic signature during installation of a VPN driver via the TeamViewer_service.exe component of TeamViewer Remote Clients prior version 15.58.4 for Windows allows an attacker with local unprivileged access on a Windows system to elevate their privileges and install drivers.
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 confidenceA vulnerability in TeamViewer Remote Client for Windows prior to 15.58.4 allows improper cryptographic signature verification during VPN driver installation via the TeamViewer_service.exe component. A local unprivileged attacker can exploit this to elevate privileges and install arbitrary drivers on the affected Windows system.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify TeamViewer installationCheck if TeamViewer is installed on the system by looking for TeamViewer_service.exe in typical installation paths (e.g., C:\Program Files\TeamViewer\TeamViewer_service.exe or C:\Program Files (x86)\TeamViewer\TeamViewer_service.exe) or via registry at HKLM\SOFTWARE\TeamViewerAffected if TeamViewer_service.exe is present on the system
-
Determine installed TeamViewer versionRight-click TeamViewer_service.exe, select Properties, then look at the Details tab for Product Version, or run 'teamviewer.exe info' from command line, or check registry key HKLM\SOFTWARE\TeamViewer\VersionAffected if The installed version is lower than 15.58.4 (e.g., 15.x versions before 15.58.4)
-
Check if VPN driver feature is enabledLook for TeamViewer VPN driver files (TeamViewer_VPN.sys or similar) in the system drivers directory (C:\Windows\System32\drivers\) or check TeamViewer settings/registry for VPN functionality statusAffected if The TeamViewer VPN driver is installed or the VPN feature has been used/enabled on the client
A system is affected if TeamViewer Remote Client for Windows is installed with a version lower than 15.58.4 AND the VPN driver feature has been used or enabled, allowing a local attacker to exploit improper signature verification during driver installation.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate TeamViewer Remote Client to version 15.58.4 or later to remediate this vulnerability.
TeamViewer version 15.58.4 or later for Windows
- Download the latest version of TeamViewer for Windows from the official website (www.teamviewer.com)
- Close any running TeamViewer instances on the system
- Run the TeamViewer installer to update the installation
- Follow the on-screen prompts to complete the upgrade to version 15.58.4 or later
- Restart the TeamViewer service if prompted
- Verify the installed version is 15.58.4 or higher by opening TeamViewer and checking About > Check version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7479 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7479 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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