Sicherheitslücken in ansible-core

Ansible-core: argument injection in ansible-galaxy role install leads to arbitrary code execution

A flaw was found in ansible-core. The ansible-galaxy role install command processes dependency specifications from a role's meta/requirements.yml file. Due to improper neutralization of argument delimiters, a malicious role author can inject arbitrary git configuration flags through the src field. This allows arbitrary code execution on the machine of a user who installs the role via ansible-galaxy role install.

• Auf 2.16.19rc1 aktualisieren
• Auf 2.18.18rc1 aktualisieren
• Auf 2.19.11rc1 aktualisieren
• Auf 2.20.7rc1 aktualisieren
• Auf 2.21.1rc1 aktualisieren

Ansible-core: unsafe tagging bypass via hostvars object in ansible-core

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.

• Auf 2.16.14rc1 aktualisieren
• Auf 2.17.7rc1 aktualisieren
• Auf 2.18.1rc1 aktualisieren

Ansible-core: ansible-core user may read/write unauthorized content

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.

• Auf 2.14.18rc1 aktualisieren
• Auf 2.15.13rc1 aktualisieren
• Auf 2.16.13rc1 aktualisieren
• Auf 2.17.6rc1 aktualisieren
• Auf 2.18.0rc2 aktualisieren

Ansible-core: exposure of sensitive information in ansible vault files due to improper logging

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.

• Auf 2.16.13 aktualisieren
• Auf 2.17.6 aktualisieren

Ansible-core: possible information leak in tasks that ignore ansible_no_log configuration

An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG configuration in some scenarios. 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.

• Auf 2.14.14 aktualisieren
• Auf 2.14.4 aktualisieren
• Auf 2.15.9 aktualisieren
• Auf 2.16.3 aktualisieren

Ansible: template injection

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.

• Auf 2.14.12 aktualisieren
• Auf 2.15.8 aktualisieren
• Auf 2.16.1 aktualisieren

Platform: ec2_key module prints out the private key directly to the standard output

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.