conda-forge infrastructure up to 2025-04-01 Azure Token access control

Summaryinfo

A vulnerability has been found in conda-forge infrastructure up to 2025-04-01 and classified as critical. The affected element is an unknown function of the component Azure Token Handler. The manipulation leads to access control. This vulnerability is traded as CVE-2025-31484. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in conda-forge infrastructure up to 2025-04-01 and classified as very critical. This issue affects an unknown part of the component Azure Token Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-31484 since 03/28/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/03/2025). MITRE ATT&CK project uses the attack technique T1068 for this issue.

Applying the patch 70f3f09e64968d5f0a7b0525846f17cad42dd052 is able to eliminate this problem. The bugfix is ready for download at github.com.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• conda-forge

Name

• infrastructure

Version

• 2025-04-01

License

• open-source

Website

• Product: https://github.com/conda-forge/infrastructure/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion