Skip to content

Product

Copeland e3 supervisory controller firmware vulnerabilities

9 published CVES affecting Copeland e3 supervisory controller firmware, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
9
Critical
2
High
4
Medium
3
Low
0
Unscored
0
CISA KEV
0

Latest Copeland e3 supervisory controller firmware CVEs

Newest publication first

  1. HighCVSS 8.6 EPSS 0.22%

    E3 Site Supervisor Control (firmware version < 2.31F01) firmware upgrade packages are unsigned. An attacker can forge malicious firmware upgrade packages. An attacker with admin access to the application services can install a malicious firmware upgrade.

  2. CriticalCVSS 9.2 EPSS 0.49%

    E3 Site Supervisor Control (firmware version < 2.31F01) generates the root linux password on each boot. An attacker can generate the root linux password for a vulnerable device based on known or easy to fetch parameters.

  3. MediumCVSS 6.9 EPSS 0.36%

    E3 Site Supervisor Control (firmware version < 2.31F01) contains a hidden API call in the application services that enables SSH and Shellinabox, which exist but are disabled by default. An attacker with admin access to the application services can utilize this API to enable remot...

  4. HighCVSS 8.7 EPSS 0.34%

    E3 Site Supervisor Control (firmware version < 2.31F01) MGW contains an API call that lacks input validation. An attacker can use this command to continuously crash the application services.

  5. MediumCVSS 5.1 EPSS 0.20%

    E3 Site Supervisor Control (firmware version < 2.31F01) has a floor plan feature that allows for an unauthenticated attacker to upload floor plan files. By uploading a specially crafted floor plan file, an attacker can inject a stored XSS to the floorplan web page.

  6. HighCVSS 8.8 EPSS 0.36%

    E3 Site Supervisor Control (firmware version < 2.31F01) has a floor plan feature that allows for an unauthenticated attacker to upload floor plan files. By uploading a specially crafted floor plan file, an attacker can access any file from the E3 file system.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.