{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-13699 exists.","fix":"No fix has been published for CVE-2020-13699 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-13699 is a high-severity command injection vulnerability in n/a, published on 29 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-13699 and fix it if it is affected.\n\nWhat it is: CVE-2020-13699 is a high-severity command injection vulnerability in n/a, published on 29 Jul 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-13699 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-13699/ (Markdown: https://insights.sbomify.com/CVE-2020-13699/index.md)","id":"CVE-2020-13699","markdown":"https://insights.sbomify.com/CVE-2020-13699/index.md","name":"CVE-2020-13699","record":{"aliases":["GHSA-f43w-mfrf-mv66"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TeamViewer Desktop","requires_auth":"none","summary":"Attackers can exploit improper URI quoting to force NTLM authentication requests, enabling hash capture or relay attacks against TeamViewer users.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"teamviewer","vendor":"teamviewer"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"TeamViewer Desktop for Windows before 15.8.3 does not properly quote its custom URI handlers. A malicious website could launch TeamViewer with arbitrary parameters, as demonstrated by a teamviewer10: --play URL. An attacker could force a victim to send an NTLM authentication request and either relay the request or capture the hash for offline password cracking. This affects teamviewer10, teamviewer8, teamviewerapi, tvchat1, tvcontrol1, tvfiletransfer1, tvjoinv8, tvpresent1, tvsendfile1, tvsqcustomer1, tvsqsupport1, tvvideocall1, and tvvpn1. The issue is fixed in 8.0.258861, 9.0.258860, 10.0.258873, 11.0.258870, 12.0.258869, 13.2.36220, 14.2.56676, 14.7.48350, and 15.8.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2021-12-26","github_poc":1,"max_poc_stars":0,"metasploit":1,"nuclei":0,"refs":[{"date":"2021-12-26T00:06:27Z","kind":"github_poc","ref":"https://github.com/Dilshan-Eranda/CVE-2020-13699","stars":0,"title":null},{"date":null,"kind":"metasploit","ref":"auxiliary/server/teamviewer_uri_smb_redirect","stars":null,"title":"TeamViewer Unquoted URI Handler SMB Redirect"}],"tier":"weaponised"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2020-13699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"acf-to-rest-api plugin insecure direct object reference (IDOR) via permalink manipulation","id":"CVE-2020-13700"},"packages":[],"prev":{"headline":"NanoHTTPD Cross-site Scripting vulnerability","id":"CVE-2020-13697"},"products":["n/a"],"published":"2020-07-29","related":[{"cvss_score":7,"headline":"TeamViewer Desktop Bypass Remote Login","id":"CVE-2019-18988","kev_date_added":"2021-11-03","published":"2020-02-07"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2018-16550","kev_date_added":null,"published":"2018-09-05"},{"cvss_score":9.3,"headline":"Path traversal in n/a","id":"CVE-2010-3128","kev_date_added":null,"published":"2010-08-26"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-14333","kev_date_added":null,"published":"2018-07-17"},{"cvss_score":7.8,"headline":"Memory corruption in TeamViewer","id":"CVE-2021-34858","kev_date_added":null,"published":"2022-01-13"},{"cvss_score":7.8,"headline":"Memory corruption in TeamViewer","id":"CVE-2021-34859","kev_date_added":null,"published":"2021-10-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can exploit improper URI quoting to force NTLM authentication requests, enabling hash capture or relay attacks against TeamViewer users.","url":"https://insights.sbomify.com/CVE-2020-13699/"}