EasympApplication · Epson

CVE-2017-12861

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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

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 confidence

Epson EasyMP projectors use a 4-digit PIN code (only 10,000 possible combinations) displayed on-screen for authentication. The vulnerability allows remote network attackers to brute-force this PIN and gain unauthorized control of the projector to stream content or issue commands.

MitigationIsolate EasyMP-enabled projectors on a separate network segment (VLAN) to limit exposure to untrusted network actors; consider disabling EasyMP if not required, and monitor for anomalous connection attempts.

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
EasympApplication
Affected:= 2.86

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify EasyMP projector on network
    Scan the network for Epson projectors with EasyMP service enabled. Use network scanning tools or check device inventory for 'Epson EasyMP' entries. Common ports include 8000 and 8080 for EasyMP services.
    Affected if An Epson projector with EasyMP functionality is found on the network
  2. Verify EasyMP version
    Access the projector's web interface or check the EasyMP software version. The version is typically displayed in the projector's settings menu under 'Network' or 'EasyMP' settings. Compare the installed version against 2.86.
    Affected if The installed EasyMP version is exactly 2.86
  3. Confirm EasyMP network features are enabled
    Check the projector's network settings to confirm EasyMP Network Projection or similar remote projection options are turned on. Look for settings like 'EasyMP Network Projection', 'EMP NS Connection', or 'PJLink' that enable remote projector control.
    Affected if EasyMP network projection features are enabled on the projector
  4. Assess network exposure
    Determine if the projector is reachable from untrusted network segments. Check network segmentation and firewall rules to see if ports used by EasyMP (such as 8000, 8080) are exposed to untrusted networks.
    Affected if The projector is accessible from untrusted or guest network segments without proper isolation

The environment is affected if an Epson EasyMP projector version 2.86 has EasyMP network features enabled and is accessible from untrusted network segments, making it vulnerable to PIN brute-force attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate EasyMP-enabled projectors on a separate network segment (VLAN) to limit exposure to untrusted network actors; consider disabling EasyMP if not required, and monitor for anomalous connection attempts.

Fix this in Easymp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12861 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-12861 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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