Local RHSM password disclosure via retry logging
Published Aug 26, 2022 · Updated Aug 3, 2024
Cleartext credential exposure in OpenStack TripleO Heat Templates before 8.4.1 allows local users to read RHSM passwords from deployment logs. The legacy rhel-registration workflow leaves its subscription-manager password unredacted when a failed task writes retry data and log output. Exposure requires an OSP13 deployment using subscription-manager and grants access to the recorded RHSM credential without altering or interrupting the deployment.
Summary
What happened
Cleartext credential exposure in OpenStack TripleO Heat Templates before 8.4.1 allows local users to read RHSM passwords from deployment logs. The legacy rhel-registration workflow leaves its subscription-manager password unredacted when a failed task writes retry data and log output. Exposure requires an OSP13 deployment using subscription-manager and grants access to the recorded RHSM credential without altering or interrupting the deployment.
The record
- CVE
- CVE-2021-3585
- Published
- Aug 26, 2022
- Updated
- Aug 3, 2024
- Vendor
- OpenStack
- Product
- TripleO Heat Templates
- Classifications
- CWE-200, CWE-312, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 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=Fixed in openstack-tripleo-heat-templates-8.4.1
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