← Back

Ansible Engine

ansible_engine

Vendor: Redhat • 25 CVEs

CVEs (25)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
3Canonical
DebianRedhat
9Ansible Engine
Debian LinuxGluster Storage+6 more
Nov 21, 2024
Jul 19, 2018
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
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...Show more
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.Show less
4Canonical
DebianRedhat+1 more
10Ansible Engine
Ceph StorageDebian Linux+7 more
Nov 21, 2024
Jul 13, 2018
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
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 execu...Show more
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.Show less
3Canonical
DebianRedhat
6Ansible Engine
CloudformsDebian Linux+3 more
Nov 21, 2024
Jul 3, 2018
N/A· v4
5.9 MEDIUM· v3
4.3 MEDIUM· v2
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...Show more
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.Show less
1Redhat
4Ansible Engine
OpenstackVirtualization+1 more
Nov 21, 2024
Jul 2, 2018
N/A· v4
7.8 HIGH· v3
4.6 MEDIUM· v2
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.
3Debian
ParamikoRedhat
11Ansible Engine
CloudformsDebian Linux+8 more
Jun 17, 2026
Mar 13, 2018
N/A· v4
9.8 CRITICAL· v3
7.5 HIGH· v2
transport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not properly chec...Show more
transport.py in the SSH server implementation of Paramiko before 1.17.6, 1.18.x before 1.18.5, 2.0.x before 2.0.8, 2.1.x before 2.1.5, 2.2.x before 2.2.3, 2.3.x before 2.3.2, and 2.4.x before 2.4.1 does not properly check whether authentication is completed before processing other requests, as demonstrated by channel-open. A customized SSH client can simply skip the authentication step.Show less