Admin code execution via unsigned firmware
Published Sep 2, 2025 · Updated Sep 2, 2025
Improper signature verification in Copeland E3 Supervisory Control before 2.31F01 allows remote authenticated users to install forged firmware. The firmware upgrade path accepts packages without verifying a vendor cryptographic signature, so attacker-supplied system code is treated as an authentic update. Administrator access to the network-reachable application services is required; successful installation executes attacker-controlled code and can alter controller functions.
Summary
What happened
Improper signature verification in Copeland E3 Supervisory Control before 2.31F01 allows remote authenticated users to install forged firmware. The firmware upgrade path accepts packages without verifying a vendor cryptographic signature, so attacker-supplied system code is treated as an authentic update. Administrator access to the network-reachable application services is required; successful installation executes attacker-controlled code and can alter controller functions.
The record
- CVE
- CVE-2025-52550
- Published
- Sep 2, 2025
- Updated
- Sep 2, 2025
- Vendor
- Copeland LP
- Product
- E3 Supervisory Control
- Classifications
- CWE-347, CAPEC-549, T1601.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Sep 2, 2025CVE publishedPublication date reported by the CVE source.
- Sep 2, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.31F01
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo