Red Hat Ansible Automation Platform
Recent Red Hat Ansible Automation Platform Security Advisories
| Advisory | Title | Published |
|---|---|---|
| RHSA-2022:6078 | (RHSA-2022:6078) Important: Red Hat Ansible Automation Platform 2.1.3 security and bug fix update | August 16, 2022 |
| RHSA-2022:6079 | (RHSA-2022:6079) Important: Red Hat Ansible Automation Platform 2.2.0 Product Security Update | August 16, 2022 |
| RHSA-2022:5703 | (RHSA-2022:5703) Important: Red Hat Ansible Automation Platform 1.2 security update | July 25, 2022 |
| RHSA-2022:5702 | (RHSA-2022:5702) Important: Red Hat Ansible Automation Platform 2.1.2 security and bug fix update | July 25, 2022 |
| RHSA-2022:0474 | (RHSA-2022:0474) Important: Red Hat Ansible Automation Platform 2.0 ansible-runner security update | February 8, 2022 |
| RHSA-2022:0460 | (RHSA-2022:0460) Important: Red Hat Ansible Automation Platform 2.1 ansible-runner security update | February 8, 2022 |
| RHSA-2021:3874 | (RHSA-2021:3874) Important: Red Hat Ansible Automation Platform 2.0.1 Security and Bug fix Release | October 15, 2021 |
By the Year
In 2023 there have been 0 vulnerabilities in Red Hat Ansible Automation Platform . Last year Ansible Automation Platform had 5 security vulnerabilities published. Right now, Ansible Automation Platform is on track to have less security vulnerabilities in 2023 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2023 | 0 | 0.00 |
| 2022 | 5 | 6.02 |
| 2021 | 4 | 5.65 |
| 2020 | 0 | 0.00 |
| 2019 | 0 | 0.00 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Ansible Automation Platform vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Red Hat Ansible Automation Platform Security Vulnerabilities
The collection remote for pulp_ansible stores tokens in plaintext instead of using pulp's encrypted field and exposes them in read/write mode
CVE-2022-3644
5.5 - Medium
- October 25, 2022
The collection remote for pulp_ansible stores tokens in plaintext instead of using pulp's encrypted field and exposes them in read/write mode via the API () instead of marking it as write only.
Insufficiently Protected Credentials
Cross site scripting in automation controller UI in Red Hat Ansible Automation Platform 1.2 and 2.0 where the project name is susceptible to XSS injection
CVE-2022-3205
6.1 - Medium
- September 13, 2022
Cross site scripting in automation controller UI in Red Hat Ansible Automation Platform 1.2 and 2.0 where the project name is susceptible to XSS injection
XSS
An Improper Certificate Validation attack was found in Openshift
CVE-2022-1632
6.5 - Medium
- September 01, 2022
An Improper Certificate Validation attack was found in Openshift. A re-encrypt Route with destinationCACertificate explicitly set to the default serviceCA skips internal Service TLS certificate validation. This flaw allows an attacker to exploit an invalid certificate, resulting in a loss of confidentiality.
Improper Certificate Validation
A privilege escalation flaw was found in the Ansible Automation Platform
CVE-2022-2568
6.5 - Medium
- August 18, 2022
A privilege escalation flaw was found in the Ansible Automation Platform. This flaw allows a remote authenticated user with 'change user' permissions to modify the account settings of the superuser account and also remove the superuser privileges.
Improper Privilege Management
A flaw was found in Ansible Galaxy Collections
CVE-2021-3681
5.5 - Medium
- April 18, 2022
A flaw was found in Ansible Galaxy Collections. When collections are built manually, any files in the repository directory that are not explicitly excluded via the ``build_ignore`` list in "galaxy.yml" include files in the ``.tar.gz`` file. This contains sensitive info, such as the user's Ansible Galaxy API key and any secrets in ``ansible`` or ``ansible-playbook`` verbose output without the``no_log`` redaction. Currently, there is no way to deprecate a Collection Or delete a Collection Version. Once published, anyone who downloads or installs the collection can view the secrets.
Insufficiently Protected Credentials
A flaw was found in Ansible, where a user's controller is vulnerable to template injection
CVE-2021-3583
7.1 - High
- September 22, 2021
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.
Code Injection
A flaw was found in Ansible if an ansible user sets ANSIBLE_ASYNC_DIR to a subdirectory of a world writable directory
CVE-2021-3533
2.5 - Low
- June 09, 2021
A flaw was found in Ansible if an ansible user sets ANSIBLE_ASYNC_DIR to a subdirectory of a world writable directory. When this occurs, there is a race condition on the managed machine. A malicious, non-privileged account on the remote machine can exploit the race condition to access the async result data. This flaw affects Ansible Tower 3.7 and Ansible Automation Platform 1.2.
Race Condition
A flaw was found in Ansible where the secret information present in async_files are getting disclosed when the user changes the jobdir to a world readable directory
CVE-2021-3532
5.5 - Medium
- June 09, 2021
A flaw was found in Ansible where the secret information present in async_files are getting disclosed when the user changes the jobdir to a world readable directory. Any secret information in an async status file will be readable by a malicious user on that system. This flaw affects Ansible Tower 3.7 and Ansible Automation Platform 1.2.
Incorrect Permission Assignment for Critical Resource
A flaw was found in the Ansible Engine 2.9.18
CVE-2021-20228
7.5 - High
- April 29, 2021
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.
Information Disclosure
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Debian Linux or by Red Hat? Click the Watch button to subscribe.
