Infrastructure
Approved changes feed: RSS · Atom
cpe:2.3:a:conda-forge:infrastructure:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Conda Forge (90e18dab-0b1d-563a-b87e-e1be0566beef) |
|---|---|
| Product | Infrastructure (7fe51da3-2a2f-5a86-a4ba-31cdf25ff994) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-31484 |
vulnerable | 2026-06-08 07:18:57.914566 |
conda-forge infrastructure uses a bad token for Azure's cf-staging access
conda-forge infrastructure holds common configurations and settings for key pieces of the conda-forge infrastructure.
Between 2025-02-10 and 2025-04-01, conda-forge infrastructure used the wrong token for Azure's cf-staging access. This bug meant that any feedstock maintainer could upload a package to the conda-forge channel, bypassing our feedstock-token + upload process. The security logs on anaconda.org were check for any packages that were not copied from the cf-staging to the conda-forge channel and none were found.
Published: 2025-04-02T21:38:03.493Z
Updated: 2025-04-03T19:38:18.563Z |
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.