{"uuid": "20a53f13-a28c-4ca3-85f6-6120894286e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-31484", "type": "seen", "source": "https://t.me/cvedetector/21918", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-31484 - Conda-Forge Azure CF-Staging Token Exposure\", \n  \"Content\": \"CVE ID : CVE-2025-31484 \nPublished : April 2, 2025, 10:15 p.m. | 20\u00a0minutes ago \nDescription : 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. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-03T01:01:24.000000Z"}