by Kastro
Paper/Archive/CVE-2025-31484

CVE-2025-31484

conda-forge infrastructure — conda-forge infrastructure uses a bad token for Azure's cf-staging access

EPSS 0.4%CVSS 9.3
critical.is priorityof 100
35
CVSS 9.3 (CNA)9.3 / 10 × 3027.9Not in CISA KEV+300.0EPSS percentile 35.9.359 × 207.2No public exploit+100.0SSVC exploitation: none+100.0
Description · from the CVE record

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.

Affected

ProductAffectedFixed inSource
infrastructure>= 2025-02-10, <= 2025-04-01–CNA

Scores by source

GitHub_M (CNA)9.3CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CISA ADPSSVCExploitation: none · Automatable: yes · Technical impact: total

References

refgithub.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72refgithub.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052