Local information disclosure via world-readable Ansible log
Published May 6, 2021 · Updated Aug 3, 2024
Information disclosure in tripleo-ansible as shipped in Red Hat OpenStack Platform 16.1 allows local users to read its Ansible deployment log. Stack creation and update place ansible.log on the undercloud with permissions that allow every local account to read data recorded by the playbook. Access requires a local account on the undercloud, and the published impact is limited to disclosure of log contents.
Summary
What happened
Information disclosure in tripleo-ansible as shipped in Red Hat OpenStack Platform 16.1 allows local users to read its Ansible deployment log. Stack creation and update place ansible.log on the undercloud with permissions that allow every local account to read data recorded by the playbook. Access requires a local account on the undercloud, and the published impact is limited to disclosure of log contents.
The record
- CVE
- CVE-2021-31918
- Published
- May 6, 2021
- Updated
- Aug 3, 2024
- Vendor
- OpenStack
- Product
- tripleo-ansible
- Classifications
- CWE-200, CWE-732, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 6, 2021CVE 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=As shipped in Red Hat Openstack 16.1
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