Search for packages
| purl | pkg:deb/debian/ansible@7.7.0%2Bdfsg-3%2Bdeb12u1?distro=trixie |
| Vulnerability | Summary | Fixed by |
|---|---|---|
| This package is not known to be affected by vulnerabilities. | ||
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-1wv8-rvwu-nye3 | 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. |
CVE-2024-9902
GHSA-32p4-gm2c-wmch |
| VCID-2jy6-eqpn-wbce | 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. |
CVE-2020-25636
PYSEC-2020-221 |
| VCID-2v57-zem6-47hq | runner/connection_plugins/ssh.py in Ansible before 1.2.3, when using ControlPersist, allows local users to redirect a ssh session via a symlink attack on a socket file with a predictable name in /tmp/. |
CVE-2013-4259
GHSA-fj24-ghp9-39v3 PYSEC-2013-1 |
| VCID-3jej-4jyp-cqbt | 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-4b5u-b82x-zkc5 | Multiple argument injection vulnerabilities in Ansible before 1.6.7 allow remote attackers to execute arbitrary code by leveraging access to an Ansible managed host and providing a crafted fact, as demonstrated by a fact with (1) a trailing " src=" clause, (2) a trailing " temp=" clause, or (3) a trailing " validate=" clause accompanied by a shell command. |
CVE-2014-4967
GHSA-64cw-m57j-65xj PYSEC-2020-205 |
| VCID-4pht-n5pc-f3gw | 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. |
CVE-2024-8775
GHSA-jpxc-vmjf-9fcj |
| VCID-5hwt-gkgx-jqb4 | Ansible 2.5 prior to 2.5.5, and 2.4 prior to 2.4.5, do not honor the no_log task flag for failed tasks. When the no_log flag has been used to protect sensitive data passed to a task from being logged, and that task does not run successfully, Ansible will expose sensitive data in log files and on the terminal of the user running Ansible. |
CVE-2018-10855
GHSA-jwcc-j78w-j73w PYSEC-2018-42 |
| VCID-682j-e2pu-1uee | 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. |
CVE-2023-5764
GHSA-7j69-qfc3-2fq9 |
| VCID-7sp5-368w-w3fd | The safe_eval function in Ansible before 1.6.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrary code via crafted instructions. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-4657. |
CVE-2014-4678
GHSA-66c7-5pwv-mm3j PYSEC-2020-203 |
| VCID-8pn7-4k42-6qeb | Ansible before 1.6.7 does not prevent inventory data with "{{" and "lookup" substrings, and does not prevent remote data with "{{" substrings, which allows remote attackers to execute arbitrary code via (1) crafted lookup('pipe') calls or (2) crafted Jinja2 data. |
CVE-2014-4966
GHSA-wqq5-c89p-3wc3 PYSEC-2020-204 |
| VCID-a49n-tvnt-p3df | 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-ae1r-yq1g-rkem | 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-atun-stks-4kcb | Insertion of Sensitive Information into Log File 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-axc3-wcsk-q3eg | 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-b2r5-fb4m-jbcr | Ansible before 1.2.1 makes it easier for remote attackers to conduct man-in-the-middle attacks by leveraging failure to cache SSH host keys. |
CVE-2013-2233
GHSA-9x6q-5423-w5v9 PYSEC-2018-36 |
| VCID-b8zs-br97-57av | 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-bc3y-qwxc-p3dx | Ansible prior to 1.5.4 mishandles the evaluation of some strings. |
CVE-2014-2686
GHSA-49m5-2838-q2rv PYSEC-2020-198 |
| VCID-c1d7-4rje-ayf9 | A flaw was found in the way Ansible (2.3.x before 2.3.3, and 2.4.x before 2.4.1) passed certain parameters to the jenkins_plugin module. Remote attackers could use this flaw to expose sensitive information from a remote host's logs. This flaw was fixed by not allowing passwords to be specified in the "params" argument, and noting this in the module documentation. |
CVE-2017-7550
GHSA-588w-w6mv-3cw5 PYSEC-2017-4 |
| VCID-c22m-1buy-3uc5 | The vault subsystem in Ansible before 1.5.5 does not set the umask before creation or modification of a vault file, which allows local users to obtain sensitive key information by reading a file. |
CVE-2014-4658
GHSA-5g4v-2pc6-4hh4 PYSEC-2020-200 |
| VCID-ckt2-us5z-pyef | ansible before versions 2.8.6, 2.7.14, 2.6.20 is vulnerable to a None |
CVE-2019-14856
GHSA-6fq2-x65v-v9h7 PYSEC-2019-146 |
| VCID-d4ka-dk4p-kfhb | 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-drt9-vx5r-akgm | Ansible fetch module before versions 2.5.15, 2.6.14, 2.7.8 has a path traversal vulnerability which allows copying and overwriting files outside of the specified destination in the local ansible controller host, by not restricting an absolute path. |
CVE-2019-3828
GHSA-74vq-h4q8-x6jv PYSEC-2019-5 |
| VCID-dtc3-3bxm-fkcg | The user module in ansible before 1.6.6 allows remote authenticated users to execute arbitrary commands. |
CVE-2014-3498
GHSA-4cvm-5776-jx9f PYSEC-2017-2 |
| VCID-dzdx-wae5-8ydy | Ansible leaks password to logs 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-e3z2-ydhb-gqfg | 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-ebtk-4m83-ryez | A flaw was found in Ansible Collection community.crypto. openssl_privatekey_info exposes private key in logs. This directly impacts confidentiality |
CVE-2020-25646
|
| VCID-ezaq-tqd3-4yd1 | 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-ezux-6buh-h7h7 | 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-fetz-42jf-nqe8 | An input validation vulnerability was found in Ansible's mysql_user module before 2.2.1.0, which may fail to correctly change a password in certain circumstances. Thus the previous password would still be active when it should have been changed. |
CVE-2016-8647
GHSA-x4cm-m36h-c6qj PYSEC-2018-58 |
| VCID-fj2p-7wkh-1fhq | 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-g2pj-dmae-e3er | 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-geaa-6dxx-tbcw | 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-h1n3-cmte-eugf | 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-hfxe-jjf5-nqd1 | A flaw was found in Ansible before version 2.2.0. The apt_key module does not properly verify key fingerprints, allowing remote adversary to create an OpenPGP key which matches the short key ID and inject this key instead of the correct key. |
CVE-2016-8614
GHSA-cmwx-9m2h-x7v4 PYSEC-2018-37 |
| VCID-hnjw-vehk-2fdd | Ansible before 1.9.2 does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. |
CVE-2015-3908
GHSA-w64c-pxjj-h866 PYSEC-2015-1 |
| VCID-hqar-fca3-cbht | 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-jhxm-379u-subt | Ansible before version 2.3 has an input validation vulnerability in the handling of data sent from client systems. An attacker with control over a client system being managed by Ansible, and the ability to send facts back to the Ansible server, could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges. |
CVE-2017-7466
GHSA-3m8p-xpm6-8ww3 PYSEC-2018-40 |
| VCID-jnmu-c8dt-5yb6 | 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-jrxz-b168-7ug4 | 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-jwsu-7znb-kueg | Ansible before 1.5.5 constructs filenames containing user and password fields on the basis of deb lines in sources.list, which might allow local users to obtain sensitive credential information in opportunistic circumstances by leveraging existence of a file that uses the "deb http://user:pass@server:port/" format. |
CVE-2014-4660
GHSA-5xm4-jmpw-p6j3 PYSEC-2020-202 |
| VCID-kb5h-116p-33b4 | 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-nukv-kkws-xkb1 | 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 |
| VCID-puq1-z5h7-pkdg | ansible before versions 2.5.14, 2.6.11, 2.7.5 is vulnerable to a information disclosure flaw in vvv+ mode with no_log on that can lead to leakage of sensible data. |
CVE-2018-16876
GHSA-j569-fghw-f9rx PYSEC-2019-141 |
| VCID-q4q1-aueh-sub2 | Ansible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller. An attacker with the ability to create special variables on the controller could execute arbitrary commands on Ansible clients as the user Ansible runs as. |
CVE-2016-8628
GHSA-jg4f-jqm5-4mgq PYSEC-2018-38 |
| VCID-qbdk-hxhg-wbh4 | 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. |
CVE-2025-14010
GHSA-8ggh-xwr9-3373 |
| VCID-r6bb-p28b-8fcn | Execution of Ansible playbooks on Windows platforms with PowerShell ScriptBlock logging and Module logging enabled can allow for 'become' passwords to appear in EventLogs in plaintext. A local user with administrator privileges on the machine can view these logs and discover the plaintext password. Ansible Engine 2.8 and older are believed to be vulnerable. |
CVE-2018-16859
GHSA-v735-2pp6-h86r PYSEC-2018-60 |
| VCID-rdwq-93d6-c7b4 | 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-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-rknj-nkgs-wyg2 | Ansible "User" module leaks any data which is passed on as a parameter to ssh-keygen. This could lean in undesirable situations such as passphrases credentials passed as a parameter for the ssh-keygen executable. Showing those credentials in clear text form for every user which have access just to the process list. |
CVE-2018-16837
GHSA-hwrm-63v2-42g4 PYSEC-2018-44 |
| VCID-rsry-fw45-9yev | 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-s1r4-29kw-5kbg | The create_script function in the lxc_container module in Ansible before 1.9.6-1 and 2.x before 2.0.2.0 allows local users to write to arbitrary files or gain privileges via a symlink attack on (1) /opt/.lxc-attach-script, (2) the archived container in the archive_path directory, or the (3) lxc-attach-script.log or (4) lxc-attach-script.err files in the temporary directory. |
CVE-2016-3096
GHSA-rh6x-qvg7-rrmj PYSEC-2016-1 |
| VCID-swpr-3qae-d7fe | 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-uhg5-zpzt-e3gz | 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-ujbp-cc1r-wfe9 | 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-v3h9-1t69-v7a3 | 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-v6rk-y6ws-dkh9 | 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. |
CVE-2024-11079
GHSA-99w6-3xph-cx78 |
| VCID-vdyk-rcxz-z7an | The safe_eval function in Ansible before 1.5.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrary code via crafted instructions. |
CVE-2014-4657
GHSA-qg47-5px9-32g7 PYSEC-2020-199 |
| VCID-w6be-213x-1yh3 | Ansible before 1.5.5 sets 0644 permissions for sources.list, which might allow local users to obtain sensitive credential information in opportunistic circumstances by reading a file that uses the "deb http://user:pass@server:port/" format. |
CVE-2014-4659
GHSA-6667-f46p-pg88 PYSEC-2020-201 |
| VCID-w8qm-73f3-rkbm | 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-wqm7-2ajr-6ue8 | In ansible it was found that inventory variables are loaded from current working directory when running ad-hoc command which are under attacker's control, allowing to run arbitrary code as a result. |
CVE-2018-10874
GHSA-3xvg-x47j-x75w PYSEC-2018-81 |
| VCID-x5e2-7whc-v3fc | 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-x94k-nxyd-27gs | 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-xak4-qbwg-z3b7 | lib/ansible/playbook/__init__.py in Ansible 1.2.x before 1.2.3, when playbook does not run due to an error, allows local users to overwrite arbitrary files via a symlink attack on a retry file with a predictable name in /var/tmp/ansible/. |
CVE-2013-4260
GHSA-pcqv-c46v-2p4v PYSEC-2013-2 |
| VCID-xg2f-12w4-yqge | 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-xw8r-fn6y-mbhp | 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-y91x-2rch-pkar | A flaw was found in ansible. ansible.cfg is read from the current working directory which can be altered to make it point to a plugin or a module path under the control of an attacker, thus allowing the attacker to execute arbitrary code. |
CVE-2018-10875
GHSA-fc4h-467w-46rh PYSEC-2018-43 |
| VCID-yc8n-wxb4-1uaz | Ansible before versions 2.1.4, 2.2.1 is vulnerable to an improper input validation in Ansible's handling of data sent from client systems. An attacker with control over a client system being managed by Ansible and the ability to send facts back to the Ansible server could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges. |
CVE-2016-9587
GHSA-m956-frf4-m2wr PYSEC-2018-39 |
| 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 |
| VCID-ynmp-3yfy-sfc1 | The chroot, jail, and zone connection plugins in ansible before 1.9.2 allow local users to escape a restricted environment via a symlink attack. |
CVE-2015-6240
GHSA-wwwh-47wp-m522 PYSEC-2017-3 |
| VCID-yur3-am6j-w7ay | 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-zmr4-652z-r3dm | Ansible before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated. |
CVE-2017-7481
GHSA-w578-j992-554x PYSEC-2018-41 |
| VCID-zzzs-scbg-bbe9 | 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 |