CVE-2017-12860
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.In addition to the password, each projector has a hardcoded "backdoor" code (2270), which authenticates to all devices.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEpson EasyMP projector remote streaming software contains a hardcoded backdoor password (2270) that bypasses the intended 4-digit on-screen code authentication, allowing unauthorized users to access any vulnerable projector.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.86CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Epson EasyMP software is installedCheck Program Files for an EasyMP folder, or use Control Panel Programs and Features to locate Epson EasyMP in the installed software listAffected if Epson EasyMP is present on the system
-
Determine the installed EasyMP versionRight-click the EasyMP executable, select Properties, then check the Details tab for the Product Version field; alternatively, open EasyMP and navigate to Help > About to view version infoAffected if The version listed is 2.86
-
Check if remote streaming access is enabledAccess the projector network settings or EasyMP connection configuration to verify if remote streaming or remote access functionality has been enabledAffected if Remote streaming/remote access is enabled on the projector
-
Look for the backdoor password in useAttempt to authenticate using the code 2270 as an alternative to the normal 4-digit on-screen code when connecting to a projector via EasyMP, or examine network logs for authentication attempts using this codeAffected if Authentication succeeds with code 2270 when the normal code is different
The environment is affected if Epson EasyMP version 2.86 is installed AND remote streaming access is enabled on the projector, allowing the hardcoded password 2270 to bypass normal authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataContact Epson for firmware/vendor patch to remove the hardcoded backdoor; until patched, isolate affected projectors on restricted network segments and monitor for unauthorized streaming attempts.
- Consultation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12860 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data