{"api_version":"1","generated_at":"2026-06-03T21:30:29+00:00","cve":"CVE-2019-18988","urls":{"html":"https://cve.report/CVE-2019-18988","api":"https://cve.report/api/cve/CVE-2019-18988.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2019-18988","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2019-18988"},"summary":{"title":"CVE-2019-18988","description":"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.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2020-02-07 16:15:00","updated_at":"2020-08-24 17:37:00"},"problem_types":["CWE-521"],"metrics":[],"references":[{"url":"https://twitter.com/Blurbdust/status/1224212682594770946?s=20","name":"https://twitter.com/Blurbdust/status/1224212682594770946?s=20","refsource":"MISC","tags":["Third Party Advisory"],"title":"Nic Losby na Twitterze: \"https://t.co/avUoHNCJ4G\nTeamviewer has been storing user passwords encrypted with AES, not hashed, in the registry accessible to low privilege users on the machine. This works for versions dating back from at least as far back as 2012 to the latest version.\"","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://community.teamviewer.com/t5/Announcements/Specification-on-CVE-2019-18988/td-p/82264","name":"https://community.teamviewer.com/t5/Announcements/Specification-on-CVE-2019-18988/td-p/82264","refsource":"MISC","tags":["Vendor Advisory"],"title":"Specification on CVE-2019-18988 - TeamViewer Community - 82264","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://community.teamviewer.com/t5/Knowledge-Base/tkb-p/Knowledgebase?threadtype=label&labels=Security","name":"https://community.teamviewer.com/t5/Knowledge-Base/tkb-p/Knowledgebase?threadtype=label&labels=Security","refsource":"MISC","tags":["Vendor Advisory"],"title":"Knowledge Base - Become a TeamViewer Expert","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://whynotsecurity.com/blog/teamviewer/","name":"https://whynotsecurity.com/blog/teamviewer/","refsource":"MISC","tags":["Exploit","Third Party Advisory"],"title":"WhyNotSecurity - WhyNotSecurity","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-18988","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-18988","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2019","cve_id":"18988","vulnerable":"1","versionEndIncluding":"14.7.1965","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"teamviewer","cpe5":"teamviewer","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":{"cve_year":"2019","cve_id":"18988","cve":"CVE-2019-18988","vendorProject":"TeamViewer","product":"Desktop","vulnerabilityName":"TeamViewer Desktop Bypass Remote Login Vulnerability","dateAdded":"2021-11-03","shortDescription":"TeamViewer Desktop allows for bypass of remote-login access control because the same AES key is used for different customers' installations. If an attacker were to know this key, they could decrypt protected information stored in registry or configuration files or decryption of the Unattended Access password to the system (which allows for remote login to the system).","requiredAction":"Apply updates per vendor instructions.","dueDate":"2022-05-03","knownRansomwareCampaignUse":"Unknown","notes":"https://nvd.nist.gov/vuln/detail/CVE-2019-18988","cwes":"CWE-521","catalogVersion":"2026.06.03","updated_at":"2026-06-03 17:01:29"},"epss":{"cve_year":"2019","cve_id":"18988","cve":"CVE-2019-18988","epss":"0.076290000","percentile":"0.920090000","score_date":"2026-06-02","updated_at":"2026-06-03 00:08:18"},"legacy_qids":[{"cve":"CVE-2019-18988","qid":"590595","title":"VISAM VBASE Editor Multiple Vulnerabilities (ICSA-21-308-01)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2019-18988","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"url":"https://community.teamviewer.com/t5/Knowledge-Base/tkb-p/Knowledgebase?threadtype=label&labels=Security","refsource":"MISC","name":"https://community.teamviewer.com/t5/Knowledge-Base/tkb-p/Knowledgebase?threadtype=label&labels=Security"},{"refsource":"MISC","name":"https://whynotsecurity.com/blog/teamviewer/","url":"https://whynotsecurity.com/blog/teamviewer/"},{"refsource":"MISC","name":"https://twitter.com/Blurbdust/status/1224212682594770946?s=20","url":"https://twitter.com/Blurbdust/status/1224212682594770946?s=20"},{"refsource":"MISC","name":"https://community.teamviewer.com/t5/Announcements/Specification-on-CVE-2019-18988/td-p/82264","url":"https://community.teamviewer.com/t5/Announcements/Specification-on-CVE-2019-18988/td-p/82264"}]}},"nvd":{"publishedDate":"2020-02-07 16:15:00","lastModifiedDate":"2020-08-24 17:37:00","problem_types":["CWE-521"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","attackVector":"LOCAL","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH","baseScore":7,"baseSeverity":"HIGH"},"exploitabilityScore":1,"impactScore":5.9},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:L/AC:M/Au:N/C:P/I:P/A:P","accessVector":"LOCAL","accessComplexity":"MEDIUM","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"PARTIAL","baseScore":4.4},"severity":"MEDIUM","exploitabilityScore":3.4,"impactScore":6.4,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:teamviewer:teamviewer:*:*:*:*:*:*:*:*","versionEndIncluding":"14.7.1965","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2019","CveId":"18988","Ordinal":"160554","Title":"CVE-2019-18988","CVE":"CVE-2019-18988","Year":"2019"},"notes":[{"CveYear":"2019","CveId":"18988","Ordinal":"1","NoteData":"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.","Type":"Description","Title":null},{"CveYear":"2019","CveId":"18988","Ordinal":"2","NoteData":"2020-02-07","Type":"Other","Title":"Published"},{"CveYear":"2019","CveId":"18988","Ordinal":"3","NoteData":"2020-02-07","Type":"Other","Title":"Modified"}]}}}