Session-data disclosure via hard-coded AES key
Published Sep 23, 2025 · Updated Sep 24, 2025
Use of a hard-coded key in AutomationDirect CLICK PLUS firmware before 3.71 allows remote attackers to read KOPS session setup traffic. The firmware reuses a built-in AES key to protect the initial messages of each new KOPS session instead of using a deployment-specific secret. Network access to KOPS and possession of the embedded key are sufficient to recover protected setup data; no modification or interruption is reported.
Summary
What happened
Use of a hard-coded key in AutomationDirect CLICK PLUS firmware before 3.71 allows remote attackers to read KOPS session setup traffic. The firmware reuses a built-in AES key to protect the initial messages of each new KOPS session instead of using a deployment-specific secret. Network access to KOPS and possession of the embedded key are sufficient to recover protected setup data; no modification or interruption is reported.
The record
- CVE
- CVE-2025-58069
- Published
- Sep 23, 2025
- Updated
- Sep 24, 2025
- Vendor
- AutomationDirect
- Product
- CLICK PLUS C2-x CPU firmware
- Classifications
- CWE-321, T0842
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2025CVE publishedPublication date reported by the CVE source.
- Sep 24, 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 <v3.71
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.
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