/

CVE-2021-43717

Severity:

CRITICAL RISK

(9.8)

Hard-Coded Credentials (CWE-798) in Epson iProjection App

CVE-2021-43717

Deferred

Vulnerability type

Category:

Hard-Coded Credentials

CWE:

CWE-798

Impact:

Unauthorized projector access and control

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Epson iProjection for the EH-TW5350 projector contains hard-coded authentication information that can permit unauthorized access to a projector. An attacker who can reach an affected projector through its iProjection interface may use those credentials to control the device maliciously.

Affected context

The issue occurs in Epson iProjection.apk v3.2.6 when it is used with an EH-TW5350 projector that exposes the iProjection function. Risk depends on the projector being reachable through the relevant network or device interface and on the embedded authentication information remaining valid.

Exploit preconditions

  • Attack surface: The projector's iProjection communication interface
  • Required access: Network or device-level reachability to an affected projector
  • Trigger point: Authentication to the projector using credentials embedded in the application
  • Why exploitation is possible: Authentication relies on credentials that are fixed in the application and may be discoverable or reused across deployments

Why this happens

The application contains authentication information directly in its distributable code or resources instead of obtaining unique credentials through a protected provisioning process. This maps to CWE-798, which covers the use of hard-coded credentials that can be recovered, reused, or shared across installations, weakening authentication boundaries.

Potential impact

  • An attacker may gain unauthorized access to the projector
  • An attacker could change projector settings or displayed content
  • The device may be disrupted or misused
  • The projector could serve as a foothold for further attacks against reachable systems

General mitigation guidance

Mitigation generally focuses on removing shared secrets from client

applications and strengthening device authentication.

Common defensive patterns include:

  • Using unique, device-bound credentials established through secure provisioning
  • Avoiding storage of reusable authentication secrets in APK code or resources
  • Supporting credential rotation, revocation, and reset
  • Restricting projector management interfaces to trusted networks or authorized controllers
  • Applying least privilege to projector control operations
  • Requiring authenticated and integrity-protected communication where supported
  • Treating application packages as observable and assuming embedded secrets can be recovered

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and secret-scanning rules targeting passwords, tokens, and fixed authentication values in APKs
  • Reverse engineering reviews of authentication and provisioning flows
  • Code review checks for constant credentials, fallback passwords, and shared device secrets
  • Runtime testing that compares authentication behavior across multiple devices
  • Network monitoring for unexpected projector-management connections or repeated authentication attempts
  • Policy enforcement that blocks releases containing embedded production credentials

Sources

SourceLink
github.comgithub.com/dpfkdlemtp/epson-eh-tw5350-advisories/blob/master/CVE-2021-43717.md

Frequently asked

questions

It may be exploitable over a network or other supported communication path when

an attacker can reach an affected projector's iProjection interface.

The hard-coded authentication information may allow an attacker to authenticate

without having been legitimately provisioned as an authorized controller.

Reachability and interface exposure remain important prerequisites.

Replace shared embedded credentials with unique, device-bound credentials

provisioned securely, and provide mechanisms for rotation, revocation, and reset.

Keep reusable secrets out of client packages, review authentication flows

during development, scan release artifacts for embedded credentials, and

restrict device-management interfaces to trusted users and networks.

Find out what's already
exploitable in your codebase.