Configuration traffic disclosure via hard-coded SSH key
Published Feb 4, 2022 · Updated Aug 3, 2024
Hard-coded credentials in Schneider Electric Easergy P5 firmware before 01.401.101 allow attackers to disclose configuration traffic. The firmware contains a hard-coded SSH cryptographic key that can be used after acquisition to take active control on the operational network. Exploitation requires possession of that key and control of the local operational network, where configuration traffic can be observed and manipulated.
Summary
What happened
Hard-coded credentials in Schneider Electric Easergy P5 firmware before 01.401.101 allow attackers to disclose configuration traffic. The firmware contains a hard-coded SSH cryptographic key that can be used after acquisition to take active control on the operational network. Exploitation requires possession of that key and control of the local operational network, where configuration traffic can be observed and manipulated.
The record
- CVE
- CVE-2022-22722
- Published
- Feb 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- Schneider Electric
- Product
- Easergy P5
- Classifications
- CWE-798, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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=unspecified <01.401.101
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