{"uuid": "df5648fc-2b3b-4a1e-b4e2-c1d05ad985d2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-31484", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/10155", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-31484\n\ud83d\udd25 CVSS Score: 9.3 (cvssV4_0, Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N)\n\ud83d\udd39 Description: 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.\n\ud83d\udccf Published: 2025-04-02T21:38:03.493Z\n\ud83d\udccf Modified: 2025-04-02T21:38:03.493Z\n\ud83d\udd17 References:\n1. https://github.com/conda-forge/infrastructure/security/advisories/GHSA-m4h2-49xf-vq72\n2. https://github.com/conda-forge/infrastructure/commit/70f3f09e64968d5f0a7b0525846f17cad42dd052", "creation_timestamp": "2025-04-02T22:34:43.000000Z"}