Ansible Exposes Sensitive Information
A flaw was found in the Ansible Engine prior to 2.10.6rc1, 2.9.18rc1, and 2.8.19rc1, where sensitive info is not masked by default and is not protected by the `no_log` feature when using the sub-option feature of the basic.py module. This flaw allows an attacker to obtain sensitive information. The highest threat from this vulnerability is to confidentiality.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2021-20228US | high7.5OT elevated | — | ||
A flaw was found in the Ansible Engine 2.9.18, where sensitive info is not masked by default and is not protected by the no_log feature when using the sub-option feature of the bas… | ||||
02
references
External citations — patches, advisories, analysis.
- https://bugzilla.redhat.com/show_bug.cgi?id=1925002WEB
- https://github.com/advisories/GHSA-5rrg-rr89-x9mvADVISORY
- https://github.com/ansible/ansiblePACKAGE
- https://github.com/ansible/ansible/commit/49ebd509df9de1c1fc1bcee00e79a835dd00662cWEB
- https://github.com/ansible/ansible/commit/e41d1f0a3fd6c466192e7e24accd3d1c6501111bWEB
- https://github.com/ansible/ansible/commit/f8ff395d817c3eddc050f809919c15dfb5796120WEB
- https://github.com/ansible/ansible/pull/73487WEB
- https://github.com/ansible/ansible/pull/73492WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan