# CVE-2018-16550: Security feature bypass in n/a

> Attackers can bypass brute-force protection in TeamViewer to easily guess the default PIN and gain unauthorized access.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3j7w-gj98-cj27

## What is CVE-2018-16550?

CVE-2018-16550 is a critical vulnerability in n/a, published on 5 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2018-16550?

It affects 1 product.


Products: Teamviewer Teamviewer.

## How do I fix CVE-2018-16550?

No fix has been published for CVE-2018-16550 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-16550 being exploited?

There is no known exploitation of CVE-2018-16550 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-18988](https://insights.sbomify.com/CVE-2019-18988/): TeamViewer Desktop Bypass Remote Login (high 7.0, exploited in the wild)
- [CVE-2010-3128](https://insights.sbomify.com/CVE-2010-3128/): Path traversal in n/a (critical 9.3)
- [CVE-2020-13699](https://insights.sbomify.com/CVE-2020-13699/): Command injection in n/a (high 8.8)
- [CVE-2018-14333](https://insights.sbomify.com/CVE-2018-14333/): Information disclosure in n/a (high 8.1)
- [CVE-2021-34858](https://insights.sbomify.com/CVE-2021-34858/): Memory corruption in TeamViewer (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16550 and fix it if it is affected.

What it is: CVE-2018-16550 is a critical vulnerability in n/a, published on 5 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16550 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-16550/ (Markdown: https://insights.sbomify.com/CVE-2018-16550/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-16550
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-16550
- OSV: https://osv.dev/vulnerability/CVE-2018-16550

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-16550/
Summaries are generated and may contain mistakes; the official description above is the record.