# CVE-2017-12861: Auth bypass in n/a

> Attackers can brute-force the 4-digit authentication code to remotely control and stream content to vulnerable Epson projectors.

- **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:** 10 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xhf5-2xwr-3gp9

## What is CVE-2017-12861?

CVE-2017-12861 is a critical authentication bypass vulnerability in n/a, published on 10 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Epson "EasyMP" software is designed to remotely stream a users computer to supporting projectors.These devices are authenticated using a unique 4-digit code, displayed on-screen - ensuring only those who can view it are streaming.All Epson projectors supporting the "EasyMP" software are vulnerable to a brute-force vulnerability, allowing any attacker on the network to remotely control and stream to the vulnerable device

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2017-12861?

It affects 1 product.


Products: Epson Easymp.

## How do I fix CVE-2017-12861?

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

## Is CVE-2017-12861 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-12860](https://insights.sbomify.com/CVE-2017-12860/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12861 and fix it if it is affected.

What it is: CVE-2017-12861 is a critical authentication bypass vulnerability in n/a, published on 10 Oct 2017. 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-2017-12861 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-2017-12861/ (Markdown: https://insights.sbomify.com/CVE-2017-12861/index.md)
```

## Sources

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

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