Proxy-password disclosure via low-entropy registry encryption
Published Jan 28, 2022 · Updated Aug 3, 2024
Insufficient entropy in Schneider Electric Software Update 2.3.0 through 2.5.1 allows local users to decrypt stored proxy passwords. SESU stores proxy credentials in the Windows Registry using a protection scheme with insufficient entropy, making the password recoverable. Local low-privileged access and configured proxy credentials are required; impact is limited to password disclosure and unintended outbound connections.
Summary
What happened
Insufficient entropy in Schneider Electric Software Update 2.3.0 through 2.5.1 allows local users to decrypt stored proxy passwords. SESU stores proxy credentials in the Windows Registry using a protection scheme with insufficient entropy, making the password recoverable. Local low-privileged access and configured proxy credentials are required; impact is limited to password disclosure and unintended outbound connections.
The record
- CVE
- CVE-2021-22799
- Published
- Jan 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-331, CAPEC-59, T1552.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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