# CVE-2021-27943: Auth bypass in n/a

> Attackers can brute-force the weak pairing code to remotely control Vizio Smart TV settings and configurations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j832-p674-7p6p

## What is CVE-2021-27943?

CVE-2021-27943 is a high-severity authentication bypass vulnerability in n/a, published on 2 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The pairing procedure used by the Vizio P65-F1 6.0.31.4-2 and E50x-E1 10.0.31.4-2 Smart TVs and mobile application is vulnerable to a brute-force attack (against only 10000 possibilities), allowing a threat actor to forcefully pair the device, leading to remote control of the TV settings and configurations.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2021-27943?

It affects 2 products.


Products: Vizio E50x-E1 Firmware, Vizio P65-F1 Firmware.

## How do I fix CVE-2021-27943?

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

## Is CVE-2021-27943 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-27944](https://insights.sbomify.com/CVE-2021-27944/): Missing authorization in n/a (critical 9.8)
- [CVE-2021-27942](https://insights.sbomify.com/CVE-2021-27942/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-27943 and fix it if it is affected.

What it is: CVE-2021-27943 is a high-severity authentication bypass vulnerability in n/a, published on 2 Aug 2021. 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-2021-27943 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-2021-27943/ (Markdown: https://insights.sbomify.com/CVE-2021-27943/index.md)
```

## Sources

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

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