CVE-2025-31484

{"cve": {"data_type": "CVE", "references": {"reference_data": [{"url": "https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052", "name": "https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052", "tags": [], "refsource": ""}, {"url": "https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72", "name": "https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72", "tags": [], "refsource": ""}]}, "data_format": "MITRE", "description": {"description_data": [{"lang": "en", "value": "conda-forge infrastructure holds common configurations and settings for key pieces of the conda-forge infrastructure.\nBetween 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."}]}, "problemtype": {"problemtype_data": [{"description": [{"lang": "en", "value": "CWE-284"}]}]}, "data_version": "4.0", "CVE_data_meta": {"ID": "CVE-2025-31484", "ASSIGNER": "security-advisories@github.com"}}, "impact": {}, "publishedDate": "2025-04-02T22:15Z", "configurations": {"nodes": [], "CVE_data_version": "4.0"}, "lastModifiedDate": "2025-04-02T22:15Z"}