LiveActive security incident?Get immediate response
CVE Record

CVE-2019-18988: TeamViewer Desktop through 14.7.1965 allows a bypass of remote-login access control because the same key is...

TeamViewer Desktop through 14.7.1965 allows a bypass of remote-login access control because the same key is used for different customers' installations. It used a shared AES key for all installations since at least as far back as v7.0.43148, and used it for at least OptionsPasswordAES in the current version of the product. If an attacker were to know this key, they could decrypt protect information stored in the registry or configuration files of TeamViewer. With versions before v9.x , this allowed for attackers to decrypt the Unattended Access password to the system (which allows for remote login to the system as well as headless file browsing). The latest version still uses the same key for OptionPasswordAES but appears to have changed how the Unattended Access password is stored. While in most cases an attacker requires an existing session on a system, if the registry/configuration keys were stored off of the machine (such as in a file share or online), an attacker could then decrypt the required password to login to the system.

HighCVSS 7Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

TeamViewer Desktop used a shared encryption key across customer installations. If an attacker can obtain stored TeamViewer registry or configuration data, they may decrypt protected settings and, in older versions, unattended access passwords used for remote login.

Executive priority

Treat this as a high-priority remote access risk because CISA lists it as known exploited. Prioritize discovery, credential rotation, and vendor-guided remediation on systems using unattended access or legacy TeamViewer versions.

Technical view

CVE-2019-18988 affects TeamViewer Desktop through 14.7.1965. The CVE describes shared AES-key use for OptionsPasswordAES since at least v7.0.43148. Pre-9.x versions could expose unattended access passwords. CVSS is 7.0 with local, privileged preconditions.

Likely exposure

Highest concern is endpoints running TeamViewer Desktop through 14.7.1965, especially pre-9.x installations, with unattended access enabled or exported registry/configuration files stored in shared or online locations.

Exploitation context

CISA KEV lists this CVE, so known exploitation is supported. Sources indicate attackers usually need existing system access, unless TeamViewer configuration or registry data is available off-machine.

Researcher notes

The provided CVE data has incomplete affected-product metadata, but the title and description identify TeamViewer Desktop through 14.7.1965. Do not assume a specific patch version beyond vendor guidance from the cited sources.

Mitigation direction

  • Inventory TeamViewer Desktop versions and prioritize systems through 14.7.1965.
  • Upgrade or remediate according to current TeamViewer security guidance.
  • Rotate unattended access credentials and TeamViewer-protected settings where exposure is possible.
  • Remove exported TeamViewer registry or configuration data from shared or online storage.
  • Disable unattended access where it is not operationally required.
  • Restrict and monitor TeamViewer usage on managed endpoints.

Validation and detection

  • Confirm whether TeamViewer Desktop is installed and identify exact versions.
  • Check for pre-9.x deployments and unattended access configuration.
  • Look for exported TeamViewer registry or configuration files outside endpoints.
  • Review remote access logs for unexpected TeamViewer connections.
  • Verify credential rotation after remediation.
  • Confirm vendor guidance was reviewed for the deployed version.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-521: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-18988 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7 (3.1)
Known Exploited
Yes
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7High
CVSS 3.1 vector shape for CVE-2019-18988Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-521 · source CWE mapping

Weak Password Requirements

Weak Password Requirements represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.