PLC password recovery via weak protocol encryption
Published Aug 31, 2022 · Updated Apr 16, 2025
Inadequate encryption in LS ELECTRIC XG5000 before 4.0 and affected PLC firmware allows attackers to recover PLC passwords. The XG5000-to-PLC protocol protects transmitted passwords with encryption weak enough to reverse from captured communication traffic. Attackers must capture a password-bearing exchange; the recovered credential grants full access to the affected PLC.
Summary
What happened
Inadequate encryption in LS ELECTRIC XG5000 before 4.0 and affected PLC firmware allows attackers to recover PLC passwords. The XG5000-to-PLC protocol protects transmitted passwords with encryption weak enough to reverse from captured communication traffic. Attackers must capture a password-bearing exchange; the recovered credential grants full access to the affected PLC.
The record
- CVE
- CVE-2022-2758
- Published
- Aug 31, 2022
- Updated
- Apr 16, 2025
- Vendor
- LS ELECTRIC
- Product
- XGK-CPUU/H/A/S/E
- Classifications
- CWE-326, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 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=All versions <V3.50
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