Root escalation via insecure SSH permissions
Published Jul 8, 2025 · Updated Jul 8, 2025
Improper privilege management in Phoenix Contact CHARX SEC-3xxx firmware before 1.7.3 allows local users to gain root access via SSH. Phoenix Contact states only that insecure permissions reachable through SSH let a low-privileged account elevate to root; no file, command, or permission boundary is publicly identified. Exploitation requires a local low-privilege account on an affected charging controller and grants full control of the embedded device.
Summary
What happened
Improper privilege management in Phoenix Contact CHARX SEC-3xxx firmware before 1.7.3 allows local users to gain root access via SSH. Phoenix Contact states only that insecure permissions reachable through SSH let a low-privileged account elevate to root; no file, command, or permission boundary is publicly identified. Exploitation requires a local low-privilege account on an affected charging controller and grants full control of the embedded device.
The record
- CVE
- CVE-2025-24006
- Published
- Jul 8, 2025
- Updated
- Jul 8, 2025
- Vendor
- Phoenix Contact
- Product
- CHARX SEC-3100
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Jul 8, 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.0.0 <1.7.3
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