Credential disclosure via plaintext log entries
Published Feb 4, 2022 · Updated Aug 3, 2024
Information disclosure in VMware Cloud Foundation 4.x before 4.3.1.1 and 3.x before 3.11 allows local users to read credentials. SDDC Manager writes credentials without redaction into multiple log files, leaving reusable secrets stored in plaintext. Root access to SDDC Manager is required to read the affected logs; the documented impact is credential disclosure only.
Summary
What happened
Information disclosure in VMware Cloud Foundation 4.x before 4.3.1.1 and 3.x before 3.11 allows local users to read credentials. SDDC Manager writes credentials without redaction into multiple log files, leaving reusable secrets stored in plaintext. Root access to SDDC Manager is required to read the affected logs; the documented impact is credential disclosure only.
The record
- CVE
- CVE-2022-22939
- Published
- Feb 4, 2022
- Updated
- Aug 3, 2024
- Vendor
- VMware
- Product
- VMware Cloud Foundation
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- admin
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=VMware Cloud Foundation 4.x (before 4.3.1.1) and 3.x
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.
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