Show filters
34 Total Results
Displaying 21-30 of 34
Sort by:
Attacker Value
Unknown
CVE-2020-1734
Disclosure Date: March 03, 2020 (last updated February 21, 2025)
A flaw was found in the pipe lookup plugin of ansible. Arbitrary commands can be run, when the pipe lookup plugin uses subprocess.Popen() with shell=True, by overwriting ansible facts and the variable is not escaped by quote plugin. An attacker could take advantage and run arbitrary commands by overwriting the ansible facts.
0
Attacker Value
Unknown
CVE-2019-14864
Disclosure Date: January 02, 2020 (last updated February 21, 2025)
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.
0
Attacker Value
Unknown
CVE-2019-14858
Disclosure Date: October 14, 2019 (last updated November 27, 2024)
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.
0
Attacker Value
Unknown
CVE-2019-14846
Disclosure Date: October 08, 2019 (last updated November 27, 2024)
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.
0
Attacker Value
Unknown
CVE-2018-16876
Disclosure Date: January 03, 2019 (last updated November 27, 2024)
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.
0
Attacker Value
Unknown
CVE-2018-16859
Disclosure Date: November 29, 2018 (last updated November 27, 2024)
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.
0
Attacker Value
Unknown
CVE-2018-16837
Disclosure Date: October 23, 2018 (last updated November 27, 2024)
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.
0
Attacker Value
Unknown
CVE-2017-7528
Disclosure Date: August 22, 2018 (last updated November 27, 2024)
Ansible Tower as shipped with Red Hat CloudForms Management Engine 5 is vulnerable to CRLF Injection. It was found that X-Forwarded-For header allows internal servers to deploy other systems (using callback).
0
Attacker Value
Unknown
CVE-2016-8647
Disclosure Date: July 26, 2018 (last updated January 27, 2024)
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.
0
Attacker Value
Unknown
CVE-2017-7481
Disclosure Date: July 19, 2018 (last updated November 27, 2024)
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.
0