Search for packages
| purl | pkg:pypi/ansible@2.10.1 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-2jy6-eqpn-wbce
Aliases: CVE-2020-25636 PYSEC-2020-221 |
A flaw was found in Ansible Base when using the aws_ssm connection plugin as there is no namespace separation for file transfers. Files are written directly to the root bucket, making possible to have collisions when running multiple ansible processes. This issue affects mainly the service availability. | There are no reported fixed by versions. |
|
VCID-4yvf-k192-9fca
Aliases: CVE-2021-3533 PYSEC-2021-126 |
A flaw was found in Ansible if an ansible user sets ANSIBLE_ASYNC_DIR to a subdirectory of a world writable directory. When this occurs, there is a race condition on the managed machine. A malicious, non-privileged account on the remote machine can exploit the race condition to access the async result data. This flaw affects Ansible Tower 3.7 and Ansible Automation Platform 1.2. |
Affected by 2 other vulnerabilities. |
|
VCID-682j-e2pu-1uee
Aliases: CVE-2023-5764 GHSA-7j69-qfc3-2fq9 |
Improper Neutralization of Special Elements Used in a Template Engine A template injection flaw was found in Ansible where a user's controller internal templating operations may remove the unsafe designation from template data. This issue could allow an attacker to use a specially crafted file to introduce code injection when supplying templating data. |
Affected by 3 other vulnerabilities. Affected by 2 other vulnerabilities. |
|
VCID-axc3-wcsk-q3eg
Aliases: CVE-2021-3583 GHSA-2pfh-q76x-gwvm PYSEC-2021-358 |
A flaw was found in Ansible, where a user's controller is vulnerable to template injection. This issue can occur through facts used in the template if the user is trying to put templates in multi-line YAML strings and the facts being handled do not routinely include special template characters. This flaw allows attackers to perform command injection, which discloses sensitive information. The highest threat from this vulnerability is to confidentiality and integrity. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
VCID-e3z2-ydhb-gqfg
Aliases: CVE-2021-20228 GHSA-5rrg-rr89-x9mv PYSEC-2021-1 |
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 basic.py module. This flaw allows an attacker to obtain sensitive information. The highest threat from this vulnerability is to confidentiality. |
Affected by 0 other vulnerabilities. Affected by 6 other vulnerabilities. |
|
VCID-qbdk-hxhg-wbh4
Aliases: CVE-2025-14010 GHSA-8ggh-xwr9-3373 |
Ansible Community General Collection is vulnerable to exposure of sensitive information A flaw was found in ansible-collection-community-general. This vulnerability allows for information exposure (IE) of sensitive credentials, specifically plaintext passwords, via verbose output when running Ansible with debug modes. Attackers with access to logs could retrieve these secrets and potentially compromise Keycloak accounts or administrative access. |
Affected by 0 other vulnerabilities. Affected by 0 other vulnerabilities. |
|
VCID-ujbp-cc1r-wfe9
Aliases: CVE-2023-5115 GHSA-jpvw-p8pr-9g2x |
Ansible symlink attack vulnerability An absolute path traversal attack exists in the Ansible automation platform. This flaw allows an attacker to craft a malicious Ansible role and make the victim execute the role. A symlink can be used to overwrite a file outside of the extraction path. |
Affected by 1 other vulnerability. |
|
VCID-xw8r-fn6y-mbhp
Aliases: CVE-2021-20191 GHSA-8f4m-hccc-8qph PYSEC-2021-124 |
A flaw was found in ansible. Credentials, such as secrets, are being disclosed in console log by default and not protected by no_log feature when using those modules. An attacker can take advantage of this information to steal those credentials. The highest threat from this vulnerability is to data confidentiality. Versions before ansible 2.9.18 are affected. |
Affected by 5 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-c1xg-s3kx-gkft | A flaw was found in Ansible Engine when a file is moved using atomic_move primitive as the file mode cannot be specified. This sets the destination files world-readable if the destination file does not exist and if the file exists, the file could be changed to have less restrictive permissions before the move. This could lead to the disclosure of sensitive data. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable. |
CVE-2020-1736
GHSA-x7jh-595q-wq82 PYSEC-2020-8 |
| VCID-rg5d-st3d-nbah | A flaw was found in Ansible Base when using the aws_ssm connection plugin as garbage collector is not happening after playbook run is completed. Files would remain in the bucket exposing the data. This issue affects directly data confidentiality. |
CVE-2020-25635
GHSA-f556-49jc-4rvc PYSEC-2020-220 |
| VCID-yeea-n94x-qqch | 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. |
CVE-2020-14332
GHSA-j667-c2hm-f2wp PYSEC-2020-4 |