A flaw was found in the Ansible Engine when using module_args. Tasks executed with check mode (–check-mode) do not properly neutralize sensitive data exposed in the event data. This flaw allows unauthorized users to read this data. The highest threat from this vulnerability is to confidentiality.
Weakness
The product does not neutralize or incorrectly neutralizes output that is written to logs.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Ansible_engine |
Redhat |
2.8.0 (including) |
2.8.14 (excluding) |
| Ansible_engine |
Redhat |
2.9.0 (including) |
2.9.12 (excluding) |
| Red Hat Ansible Engine 2.8 for RHEL 7 |
RedHat |
ansible-0:2.8.15-1.el7ae |
* |
| Red Hat Ansible Engine 2.8 for RHEL 8 |
RedHat |
ansible-0:2.8.15-1.el8ae |
* |
| Ansible |
Ubuntu |
bionic |
* |
| Ansible |
Ubuntu |
focal |
* |
| Ansible |
Ubuntu |
groovy |
* |
| Ansible |
Ubuntu |
hirsute |
* |
| Ansible |
Ubuntu |
impish |
* |
| Ansible |
Ubuntu |
kinetic |
* |
| Ansible |
Ubuntu |
lunar |
* |
| Ansible |
Ubuntu |
mantic |
* |
| Ansible |
Ubuntu |
trusty |
* |
| Ansible |
Ubuntu |
trusty/esm |
* |
| Ansible |
Ubuntu |
xenial |
* |
Extended Description
This can allow an attacker to forge log entries or inject malicious content into logs.
Log forging vulnerabilities occur when:
Potential Mitigations
- Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
References