CVE-2021-33923
First published: Wed Sep 29 2021(Updated: )
Insecure permissions in Confluent Ansible (cp-ansible) 5.5.0, 5.5.1, 5.5.2 and 6.0.0 allows local attackers to access some sensitive information (private keys, state database).
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Confluent Cp-ansible | =5.5.0 | |
| Confluent Cp-ansible | =5.5.1 | |
| Confluent Cp-ansible | =5.5.2 | |
| Confluent Cp-ansible | =6.0.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2021-33923?
CVE-2021-33923 is considered to have a medium severity due to the potential unauthorized access to sensitive information.
How do I fix CVE-2021-33923?
To fix CVE-2021-33923, update Confluent Ansible to version 6.0.1 or later.
What versions of Confluent Ansible are affected by CVE-2021-33923?
CVE-2021-33923 affects Confluent Ansible versions 5.5.0, 5.5.1, 5.5.2, and 6.0.0.
What kind of sensitive information is exposed by CVE-2021-33923?
CVE-2021-33923 can expose private keys and the state database to local attackers.
Can I mitigate CVE-2021-33923 without upgrading?
Mitigating CVE-2021-33923 without upgrading is not recommended, as proper permissions configuration may not fully eliminate the risk.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/author
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/event
- agent/tags
- agent/source
- vendor/confluent
- canonical/confluent cp-ansible
- version/confluent cp-ansible/5.5.0
- version/confluent cp-ansible/5.5.1
- version/confluent cp-ansible/5.5.2
- version/confluent cp-ansible/6.0.0