Описание
Ansible does not collect garbage after playbook run
A flaw was found in Ansible Base when using the aws_ssm connection plugin as its garbage collector is not happening after the playbook run is completed. Files would remain in the bucket exposing the data. This issue directly affects data confidentiality.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2020-25635
- https://github.com/ansible-collections/community.aws/issues/222
- https://github.com/ansible-collections/community.aws/pull/237#issuecomment-1468591094
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-25635
- https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-220.yaml
Пакеты
ansible
< 2.10.1
2.10.1
Связанные уязвимости
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.
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.
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.
A flaw was found in Ansible Base when using the aws_ssm connection plu ...