TeamViewer Desktop up to 14.7.1965 AES Key Configuration File improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in TeamViewer Desktop up to 14.7.1965. It has been classified as critical. The impacted element is an unknown function of the component AES Key Handler. Performing a manipulation as part of Configuration File results in improper authentication. This vulnerability is known as CVE-2019-18988. Remote exploitation of the attack is possible. Furthermore, an exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical has been found in TeamViewer Desktop up to 14.7.1965. This affects an unknown code block of the component AES Key Handler. The manipulation as part of a Configuration File leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality. The summary by CVE 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.
The weakness was published 02/07/2020. This vulnerability is uniquely identified as CVE-2019-18988 since 11/15/2019. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. Technical details are unknown but an exploit is available.
It is declared as attacked. The CISA Known Exploited Vulnerabilities Catalog lists this issue since 11/03/2021 with a due date of 05/03/2022:
Apply updates per vendor instructions.Upgrading eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.1VulDB Meta Temp Score: 6.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.0
NVD Vector: 🔍
CNA Base Score: 7.0
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Attacked
EPSS Score: 🔍
EPSS Percentile: 🔍
KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
11/15/2019 🔍02/07/2020 🔍
02/07/2020 🔍
02/28/2025 🔍
Sources
Advisory: community.teamviewer.comStatus: Confirmed
CVE: CVE-2019-18988 (🔍)
GCVE (CVE): GCVE-0-2019-18988
GCVE (VulDB): GCVE-100-149805
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/07/2020 21:26Updated: 02/28/2025 13:12
Changes: 02/07/2020 21:26 (38), 02/07/2020 21:31 (17), 03/29/2024 07:13 (17), 04/20/2024 17:43 (12), 09/09/2024 22:29 (2), 02/05/2025 05:08 (14), 02/28/2025 13:10 (1), 02/28/2025 13:12 (4)
Complete: 🔍
Committer: lywand
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.