CVE-2020-25636
First published: Mon Oct 05 2020(Updated: )
A flaw was found in Ansible Base when using the aws_ssm connection plugin as there is no namespace separation for file transfers. Files are written directly to the root bucket, making possible to have collisions when running multiple ansible processes. This issue affects mainly the service availability.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Redhat Ansible | =2.10.1-rc2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this flaw?
The vulnerability ID for this flaw is CVE-2020-25636.
What is the severity of CVE-2020-25636?
The severity of CVE-2020-25636 is high, with a severity value of 7.1.
Which software version is affected by CVE-2020-25636?
The Redhat Ansible version 2.10.1-rc2 is affected by CVE-2020-25636.
How does CVE-2020-25636 affect file transfers in Ansible Base using the aws_ssm connection plugin?
CVE-2020-25636 does not have namespace separation for file transfers in Ansible Base using the aws_ssm connection plugin, which can lead to collisions and files being written directly to the root bucket.
Where can I find more information about CVE-2020-25636?
You can find more information about CVE-2020-25636 on Red Hat's Bugzilla page and on the GitHub issue for ansible-collections.
- collector/nvd-index
- agent/references
- agent/weakness
- agent/severity
- agent/author
- agent/type
- agent/description
- agent/event
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- agent/tags
- collector/mitre-cve
- source/MITRE
- vendor/redhat
- canonical/redhat ansible
- version/redhat ansible/2.10.1-rc2