CVE-2025-32798

{"id": "CVE-2025-32798", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.2, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "PROOF_OF_CONCEPT", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "HIGH", "attackRequirements": "NONE", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-06-16T20:15:27.200", "references": [{"url": "https://github.com/conda/conda-build/blob/834448b995eee02cf1c2e7ca97bcfa9affc77ee5/conda_build/metadata.py", "source": "security-advisories@github.com"}, {"url": "https://github.com/conda/conda-build/commit/3d87213b840774a24ab1733664d2b36664233754", "source": "security-advisories@github.com"}, {"url": "https://github.com/conda/conda-build/security/advisories/GHSA-6cc8-c3c9-3rgr", "source": "security-advisories@github.com"}, {"url": "https://github.com/conda/conda-build/security/advisories/GHSA-6cc8-c3c9-3rgr", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-94"}]}], "descriptions": [{"lang": "en", "value": "Conda-build contains commands and tools to build conda packages. Prior to version 25.4.0, the conda-build recipe processing logic has been found to be vulnerable to arbitrary code execution due to unsafe evaluation of recipe selectors. Currently, conda-build uses the eval function to process embedded selectors in meta.yaml files. This approach evaluates user-defined expressions without proper sanitization, which allows arbitrary code to be executed during the build process. As a result, the integrity of the build environment is compromised, and unauthorized commands or file operations may be performed. The vulnerability stems from the inherent risk of using eval() on untrusted input in a context intended to control dynamic build configurations. By directly interpreting selector expressions, conda-build creates a potential execution pathway for malicious code, violating security assumptions. This issue has been patched in version 25.4.0."}, {"lang": "es", "value": "Conda-build contiene comandos y herramientas para compilar paquetes conda. Antes de la versi\u00f3n 25.4.0, la l\u00f3gica de procesamiento de recetas de conda-build era vulnerable a la ejecuci\u00f3n de c\u00f3digo arbitrario debido a la evaluaci\u00f3n insegura de los selectores de recetas. Actualmente, conda-build utiliza la funci\u00f3n eval para procesar selectores incrustados en archivos meta.yaml. Este enfoque eval\u00faa expresiones definidas por el usuario sin la debida depuraci\u00f3n, lo que permite la ejecuci\u00f3n de c\u00f3digo arbitrario durante el proceso de compilaci\u00f3n. Como resultado, se compromete la integridad del entorno de compilaci\u00f3n y se pueden realizar comandos u operaciones de archivo no autorizados. La vulnerabilidad se deriva del riesgo inherente de usar eval() en entradas no confiables en un contexto dise\u00f1ado para controlar configuraciones de compilaci\u00f3n din\u00e1micas. Al interpretar directamente las expresiones del selector, conda-build crea una posible v\u00eda de ejecuci\u00f3n para c\u00f3digo malicioso, violando las suposiciones de seguridad. Este problema se ha corregido en la versi\u00f3n 25.4.0."}], "lastModified": "2025-06-17T20:50:23.507", "sourceIdentifier": "security-advisories@github.com"}