# CVE-2021-27942: Code injection in n/a

> Attackers can execute arbitrary code on Vizio Smart TVs by placing malicious files on a USB drive accessed via Smart Cast.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f4j5-954q-h2r6

## What is CVE-2021-27942?

CVE-2021-27942 is a medium-severity code injection vulnerability in n/a, published on 3 Aug 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vizio P65-F1 6.0.31.4-2 and E50x-E1 10.0.31.4-2 Smart TVs allow a threat actor to execute arbitrary code from a USB drive via the Smart Cast functionality, because files on the USB drive are effectively under the web root and can be executed.

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

It affects 2 products.


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

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

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

## Is CVE-2021-27942 being exploited?

There is no known exploitation of CVE-2021-27942 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-27943](https://insights.sbomify.com/CVE-2021-27943/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-27942 is a medium-severity code injection vulnerability in n/a, published on 3 Aug 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-27942 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-27942/ (Markdown: https://insights.sbomify.com/CVE-2021-27942/index.md)
```

## Sources

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

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