Credential disclosure via encoded secrets in FFDC logs
Published Mar 9, 2021 · Updated Sep 16, 2024
Information disclosure in Lenovo XClarity Orchestrator before 1.2.2 allows remote authenticated users to obtain LXCA credentials. During each LXCA session, the resource-manager path encodes the stored LXCA credentials and writes them into the internal FFDC service log. Exploitation requires a privileged LXCO account and an LXCA resource-manager configuration; exposure is limited to the requested service log.
Summary
What happened
Information disclosure in Lenovo XClarity Orchestrator before 1.2.2 allows remote authenticated users to obtain LXCA credentials. During each LXCA session, the resource-manager path encodes the stored LXCA credentials and writes them into the internal FFDC service log. Exploitation requires a privileged LXCO account and an LXCA resource-manager configuration; exposure is limited to the requested service log.
The record
- CVE
- CVE-2021-3417
- Published
- Mar 9, 2021
- Updated
- Sep 16, 2024
- Vendor
- Lenovo
- Product
- XClarity Orchestrator
- Classifications
- CWE-319, T1552.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 9, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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 <1.2.2
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