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.
Metrics
Affected Vendors & Products
References
History
Thu, 03 Apr 2025 20:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Wed, 02 Apr 2025 21:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
Title | conda-forge infrastructure uses a bad token for Azure's cf-staging access | |
Weaknesses | CWE-284 | |
References |
| |
Metrics |
cvssV4_0
|

Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2025-04-03T19:38:18.563Z
Reserved: 2025-03-28T13:36:51.297Z
Link: CVE-2025-31484

Updated: 2025-04-03T19:37:47.303Z

Status : Received
Published: 2025-04-02T22:15:20.720
Modified: 2025-04-02T22:15:20.720
Link: CVE-2025-31484

No data.