Search for packages
| purl | pkg:deb/debian/ansible@2.10.7%2Bmerged%2Bbase%2B2.10.17%2Bdfsg-0%2Bdeb11u1 |
| Next non-vulnerable version | 7.7.0+dfsg-3+deb12u1 |
| Latest non-vulnerable version | 7.7.0+dfsg-3+deb12u1 |
| Risk | 4.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-8jzt-jve3-yucx
Aliases: CVE-2024-8775 GHSA-jpxc-vmjf-9fcj |
Ansible vulnerable to Insertion of Sensitive Information into Log File A flaw was found in Ansible, where sensitive information stored in Ansible Vault files can be exposed in plaintext during the execution of a playbook. This occurs when using tasks such as include_vars to load vaulted variables without setting the no_log: true parameter, resulting in sensitive data being printed in the playbook output or logs. This can lead to the unintentional disclosure of secrets like passwords or API keys, compromising security and potentially allowing unauthorized access or actions. |
Affected by 0 other vulnerabilities. |
|
VCID-akcg-prtj-9bft
Aliases: CVE-2024-11079 GHSA-99w6-3xph-cx78 |
Ansible-Core vulnerable to content protections bypass A flaw was found in Ansible-Core. This vulnerability allows attackers to bypass unsafe content protections using the hostvars object to reference and execute templated content. This issue can lead to arbitrary code execution if remote data or module outputs are improperly templated within playbooks. |
Affected by 0 other vulnerabilities. |
|
VCID-xdpn-ahfy-p3ft
Aliases: CVE-2024-9902 GHSA-32p4-gm2c-wmch |
ansible-core Incorrect Authorization vulnerability A flaw was found in Ansible. The ansible-core `user` module can allow an unprivileged user to silently create or replace the contents of any file on any system path and take ownership of it when a privileged user executes the `user` module against the unprivileged user's home directory. If the unprivileged user has traversal permissions on the directory containing the exploited target file, they retain full control over the contents of the file as its owner. |
Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-19ec-wcrn-mycf | A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes "ansible-vault edit", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method write_data is called to write the existing secret in the file. This method will delete the file before recreating it insecurely. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable. |
CVE-2020-1740
GHSA-vcg8-98q8-g7mj PYSEC-2020-12 |
| VCID-1xt3-g2sm-cbdr | An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG configuration in some scenarios. It was discovered that information is still included in the output in certain tasks, such as loop items. Depending on the task, this issue may include sensitive information, such as decrypted secret values. |
CVE-2024-0690
GHSA-h24r-m9qc-pvpg PYSEC-2024-36 |
| VCID-2ncp-ksvc-f3e4 | A flaw was discovered in the way Ansible templating was implemented in versions before 2.6.18, 2.7.12 and 2.8.2, causing the possibility of information disclosure through unexpected variable substitution. By taking advantage of unintended variable substitution the content of any variable may be disclosed. |
CVE-2019-10156
GHSA-grgm-pph5-j5h7 PYSEC-2019-2 |
| VCID-4htg-c38r-2fh4 | In Ansible, all Ansible Engine versions up to ansible-engine 2.8.5, ansible-engine 2.7.13, ansible-engine 2.6.19, were logging at the DEBUG level which lead to a disclosure of credentials if a plugin used a library that logged credentials at the DEBUG level. This flaw does not affect Ansible modules, as those are executed in a separate process. |
CVE-2019-14846
GHSA-pm48-cvv2-29q5 PYSEC-2019-4 |
| VCID-5khf-99r9-fuhv | ansible-playbook -k and ansible cli tools, all versions 2.8.x before 2.8.4, all 2.7.x before 2.7.13 and all 2.6.x before 2.6.19, prompt passwords by expanding them from templates as they could contain special characters. Passwords should be wrapped to prevent templates trigger and exposing them. |
CVE-2019-10206
GHSA-cqmr-rcpr-cxh3 PYSEC-2019-145 |
| VCID-65qb-3ag2-y7c3 | A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5. When a module has an argument_spec with sub parameters marked as no_log, passing an invalid parameter name to the module will cause the task to fail before the no_log options in the sub parameters are processed. As a result, data in the sub parameter fields will not be masked and will be displayed if Ansible is run with increased verbosity and present in the module invocation arguments for the task. |
CVE-2019-14858
GHSA-h653-95qw-h2mp PYSEC-2019-171 |
| VCID-6jte-bjwy-63dr | Insertion of Sensitive Information into Log File in ansible A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality. |
CVE-2021-20180
GHSA-fh5v-5f35-2rv2 |
| VCID-84ev-sg57-tqdk | Ansible may expose private key A flaw was found in the Ansible Automation Platform. When creating a new keypair, the ec2_key module prints out the private key directly to the standard output. This flaw allows an attacker to fetch those keys from the log files, compromising the system's confidentiality, integrity, and availability. |
CVE-2023-4237
GHSA-ww3m-ffrm-qvqv |
| VCID-9rk9-scdv-jkhg | An archive traversal flaw was found in all ansible-engine versions 2.9.x prior to 2.9.7, when running ansible-galaxy collection install. When extracting a collection .tar.gz file, the directory is created without sanitizing the filename. An attacker could take advantage to overwrite any file within the system. |
CVE-2020-10691
GHSA-3c67-gc48-983w PYSEC-2020-2 |
| VCID-an7s-5adj-2ffc | A flaw was found in the Ansible Engine when the fetch module is used. An attacker could intercept the module, inject a new path, and then choose a new destination path on the controller node. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable. |
CVE-2020-1735
GHSA-gfr2-qpxh-qj9m PYSEC-2020-7 |
| VCID-b4w1-a3tp-9kft | 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. |
CVE-2023-5115
GHSA-jpvw-p8pr-9g2x |
| VCID-bda6-h5tr-ykhx | 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. |
CVE-2021-20228
GHSA-5rrg-rr89-x9mv PYSEC-2021-1 |
| VCID-d189-s5dm-pqbc | A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS command injections. This could result in a loss of confidentiality of the system among other issues. |
CVE-2019-14905
GHSA-frxj-5j27-f8rf PYSEC-2020-206 |
| VCID-d982-kvmd-pyae | Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data. |
CVE-2019-14864
GHSA-3m93-m4q6-mc6v PYSEC-2020-160 |
| VCID-dkse-a2zr-4ke7 | A flaw was found in Ansible Engine's ansible-connection module, where sensitive information such as the Ansible user credentials is disclosed by default in the traceback error message. The highest threat from this vulnerability is to confidentiality. |
CVE-2021-3620
GHSA-4r65-35qq-ch8j PYSEC-2022-164 |
| VCID-e3ms-pu5v-abcp | A flaw was found in Ansible 2.7.17 and prior, 2.8.9 and prior, and 2.9.6 and prior when using the Extract-Zip function from the win_unzip module as the extracted file(s) are not checked if they belong to the destination folder. An attacker could take advantage of this flaw by crafting an archive anywhere in the file system, using a path traversal. This issue is fixed in 2.10. |
CVE-2020-1737
GHSA-893h-35v4-mxqx PYSEC-2020-9 |
| VCID-f9b1-94pd-u7hj | A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x before 2.9.13, when installing packages using the dnf module. GPG signatures are ignored during installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability. |
CVE-2020-14365
GHSA-m429-fhmv-c6q2 PYSEC-2020-209 |
| VCID-g1au-jdu4-bbgr | 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 |
| VCID-g7w7-2jvw-d3hr | An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality. |
CVE-2020-14330
GHSA-785x-qw4v-6872 PYSEC-2020-3 |
| VCID-n58m-r94h-dyhh | 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. |
CVE-2021-20191
GHSA-8f4m-hccc-8qph PYSEC-2021-124 |
| VCID-nf9q-7p4u-8uer | A flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.9 and 2.9.6 respectively, when using ansible_facts as a subkey of itself and promoting it to a variable when inject is enabled, overwriting the ansible_facts after the clean. An attacker could take advantage of this by altering the ansible_facts, such as ansible_hosts, users and any other key data which would lead into privilege escalation or code injection. |
CVE-2020-10684
GHSA-p62g-jhg6-v3rq PYSEC-2020-207 |
| VCID-nygs-kyb8-bqc9 | A flaw was found in several ansible modules, where parameters containing credentials, such as secrets, were being logged in plain-text on managed nodes, as well as being made visible on the controller node when run in verbose mode. These parameters were not protected by the no_log feature. An attacker can take advantage of this information to steal those credentials, provided when they have access to the log files containing them. The highest threat from this vulnerability is to data confidentiality. This flaw affects Red Hat Ansible Automation Platform in versions before 1.2.2 and Ansible Tower in versions before 3.8.2. |
CVE-2021-3447
PYSEC-2021-107 |
| VCID-py5j-jxw1-byaq | A security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.11 and all Ansible 2.9.x versions prior to 2.9.7, when managing kubernetes using the k8s module. Sensitive parameters such as passwords and tokens are passed to kubectl from the command line, not using an environment variable or an input configuration file. This will disclose passwords and tokens from process list and no_log directive from debug module would not have any effect making these secrets being disclosed on stdout and log files. |
CVE-2020-1753
GHSA-86hp-cj9j-33vv PYSEC-2020-210 |
| VCID-pz99-qam1-fkbp | An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from become directive. The provided fix is insufficient to prevent the race condition on systems using ACLs and FUSE filesystems. Ansible Engine 2.7.18, 2.8.12, and 2.9.9 as well as previous versions are affected and Ansible Tower 3.4.5, 3.5.6 and 3.6.4 as well as previous versions are affected. |
CVE-2020-10744
GHSA-vp9j-rghq-8jhh PYSEC-2020-208 |
| VCID-qqy4-br8a-yyfp | A flaw was found in the Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when the ldap_attr and ldap_entry community modules are used. The issue discloses the LDAP bind password to stdout or a log file if a playbook task is written using the bind_pw in the parameters field. The highest threat from this vulnerability is data confidentiality. |
CVE-2020-1746
GHSA-j2h6-73x8-22c4 PYSEC-2020-13 |
| VCID-r3mc-rr9j-ybgh | A race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is created in /var/tmp. This directory is created with "umask 77 && mkdir -p <dir>"; this operation does not fail if the directory already exists and is owned by another user. An attacker could take advantage to gain control of the become user as the target directory can be retrieved by iterating '/proc/<pid>/cmdline'. |
CVE-2020-1733
GHSA-g4mq-6fp5-qwcf PYSEC-2020-5 |
| VCID-rb1x-4u5r-cbbf | A flaw was found in the use of insufficiently random values in Ansible. Two random password lookups of the same length generate the equal value as the template caching action for the same file since no re-evaluation happens. The highest threat from this vulnerability would be that all passwords are exposed at once for the file. This flaw affects Ansible Engine versions before 2.9.6. |
CVE-2020-10729
GHSA-r6h7-5pq2-j77h PYSEC-2021-105 |
| VCID-s1sn-6wq8-j3cd | A flaw was found in the solaris_zone module from the Ansible Community modules. When setting the name for the zone on the Solaris host, the zone name is checked by listing the process with the 'ps' bare command on the remote machine. An attacker could take advantage of this flaw by crafting the name of the zone and executing arbitrary commands in the remote host. Ansible Engine 2.7.15, 2.8.7, and 2.9.2 as well as previous versions are affected. |
CVE-2019-14904
GHSA-gwr8-5j83-483c PYSEC-2020-161 |
| VCID-sxkv-1qnq-vqad | 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 templating injection when supplying templating data. |
CVE-2023-5764
GHSA-7j69-qfc3-2fq9 |
| VCID-tn78-u8u8-w3c3 | 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. |
CVE-2021-3583
GHSA-2pfh-q76x-gwvm PYSEC-2021-358 |
| VCID-tnxg-cp25-tbay | A flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3 or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot and the decryp emains when the host is switched off. The system will be vulnerable when the system is not running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted ble. |
CVE-2020-10685
GHSA-77g3-3j5w-64w4 PYSEC-2020-1 |
| VCID-unkb-8sqm-1kax | A flaw was found in Ansible 2.7.16 and prior, 2.8.8 and prior, and 2.9.5 and prior when a password is set with the argument "password" of svn module, it is used on svn command line, disclosing to other users within the same node. An attacker could take advantage by reading the cmdline file from that particular PID on the procfs. |
CVE-2020-1739
GHSA-923p-fr2c-g5m2 PYSEC-2020-11 |
| VCID-vnqy-kh48-cybd | A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality. |
CVE-2021-20178
GHSA-wv5p-gmmv-wh9v PYSEC-2021-106 |
| VCID-x6mu-2u8u-6yae | A flaw was found in Ansible in the amazon.aws collection when using the tower_callback parameter from the amazon.aws.ec2_instance module. This flaw allows an attacker to take advantage of this issue as the module is handling the parameter insecurely, leading to the password leaking in the logs. |
CVE-2022-3697
GHSA-cpx3-93w7-457x |
| VCID-xdq6-nwpn-6ybj | A flaw was found in ansible 2.8.0 before 2.8.4. Fields managing sensitive data should be set as such by no_log feature. Some of these fields in GCP modules are not set properly. service_account_contents() which is common class for all gcp modules is not setting no_log to True. Any sensitive data managed by that function would be leak as an output when running ansible playbooks. |
CVE-2019-10217
GHSA-p75j-wc34-527c PYSEC-2019-3 |