Red Hat Ansible Galaxy 3.3.0
Approved changes feed: RSS · Atom
cpe:2.3:a:redhat:ansible_galaxy:3.3.0:*:*:*:*:*:*:*
part: a version: 3.3.0 update: *
| Vendor | Redhat (e942785a-ca89-506e-bd99-50782639cde3) |
|---|---|
| Product | Ansible Galaxy (d139c9ba-72a7-5dfa-be90-9a937571f3ac) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/ansible/galaxy |
purl2cpe | 2026-06-01 10:12:53.016588 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-3681 |
vulnerable | 2026-06-08 05:33:53.407826 |
Details available
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.
Published: 2022-04-18T16:20:37.000Z
Updated: 2024-08-03T17:01:07.697Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.