dbcve.org
TeamviewerApplication

CVE-2018-16550

CRITICAL · 9.8 CVSS v3.0 Published 2018-09-05
Fix available
A fix is available. Upgrade to after 13.2.9356 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
TeamViewer 10.x through 13.x allows remote attackers to bypass the brute-force authentication protection mechanism by skipping the "Cancel" step, which makes it easier to determine the correct value of the default 4-digit PIN.

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

TeamViewer 10.x through 13.x contains a flaw in the PIN-based authentication mechanism where the brute-force protection can be bypassed by skipping the 'Cancel' step during authentication attempts. This allows attackers to rapidly enumerate 4-digit PINs without triggering account lockouts or rate limits, making the default PIN vulnerable to offline cracking.

MitigationUpgrade TeamViewer to version 14.x or later, which addresses this authentication bypass. Additionally, enable two-factor authentication and use strong, unique passwords instead of the default 4-digit PIN.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TeamviewerApplication
Affected:>= 10.0.2551, <= 13.2.9356

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

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

  1. Verify TeamViewer is installed
    Check for TeamViewer installation on the system - look for TeamViewer executable or check installed programs list
    Affected if TeamViewer is installed and the version is within the affected range
  2. Determine installed TeamViewer version
    Locate TeamViewer and retrieve its version number - typically found in the application or via system information
    Affected if The version falls between 10.0.2551 and 13.2.9356 inclusive
  3. Confirm PIN authentication is in use
    Verify that the TeamViewer account or remote access is configured to use 4-digit PIN authentication
    Affected if PIN-based authentication is enabled for TeamViewer access

The environment is affected if TeamViewer is installed with a version between 10.0.2551 and 13.2.9356 and PIN-based authentication is configured.

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.

From vendor data
Upgrade available Upgrade to a release after 13.2.9356
Interim mitigation

Upgrade TeamViewer to version 14.x or later, which addresses this authentication bypass. Additionally, enable two-factor authentication and use strong, unique passwords instead of the default 4-digit PIN.

Fix this in Teamviewer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-16550 — 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-2018-16550 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