Project-file access via hard-coded backdoor key
Published Feb 14, 2024 · Updated May 12, 2025
Hard-coded credentials in EcoStruxure Control Expert before 16.0 allow local users to open application-password-protected project files. Its application-password logic contains an embedded backdoor key that accepts unauthorized access instead of enforcing the project password. The same component affects EcoStruxure Process Expert before 2023; exploitation requires local file access and permits protected project data to be read or altered.
Summary
What happened
Hard-coded credentials in EcoStruxure Control Expert before 16.0 allow local users to open application-password-protected project files. Its application-password logic contains an embedded backdoor key that accepts unauthorized access instead of enforcing the project password. The same component affects EcoStruxure Process Expert before 2023; exploitation requires local file access and permits protected project data to be read or altered.
The record
- CVE
- CVE-2023-6409
- Published
- Feb 14, 2024
- Updated
- May 12, 2025
- Vendor
- Distributed Data Systems
- Product
- EcoStruxure Control Expert
- Classifications
- CWE-798, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 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=Versions prior to v16.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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