{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-32797 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-32797 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32797 is a medium-severity vulnerability in conda-build, published on 16 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32797 and fix it if it is affected.\n\nWhat it is: CVE-2025-32797 is a medium-severity vulnerability in conda-build, published on 16 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-32797 in the wild and no public exploit code.\n\nAffected product: conda-build. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-32797/ (Markdown: https://insights.sbomify.com/CVE-2025-32797/index.md)","id":"CVE-2025-32797","markdown":"https://insights.sbomify.com/CVE-2025-32797/index.md","name":"CVE-2025-32797","record":{"aliases":["GHSA-vfp6-3v8g-vcmm"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Conda build tool","requires_auth":"none","summary":"Attackers with local access can exploit a race condition in conda-build to overwrite build scripts, enabling arbitrary code execution and privilege escalation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"conda-build","vendor":"anaconda"}],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-277","name":"Insecure Inherited Permissions"}],"description":"Conda-build contains commands and tools to build conda packages. Prior to version 25.3.1, the write_build_scripts function in conda-build creates the temporary build script conda_build.sh with overly permissive file permissions (0o766), allowing write access to all users. Attackers with filesystem access can exploit a race condition to overwrite the script before execution, enabling arbitrary code execution under the victim's privileges. This risk is significant in shared environments, potentially leading to full system compromise. Even with non-static directory names, attackers can monitor parent directories for file creation events. The brief window between script creation (with insecure permissions) and execution allows rapid overwrites. Directory names can also be inferred via timestamps or logs, and automation enables exploitation even with semi-randomized paths by acting within milliseconds of detection. This issue has been patched in version 25.3.1. A workaround involves restricting conda_build.sh permissions from 0o766 to 0o700 (owner-only read/write/execute). Additionally, use atomic file creation (write to a temporary randomized filename and rename atomically) to minimize the race condition window.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Conda-build Insecure Build Script Permissions Enabling Arbitrary Code Execution","id":"CVE-2025-32797","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Conda-build Allows Arbitrary Code Execution via Malicious Recipe Selectors","id":"CVE-2025-32798"},"packages":[],"prev":{"headline":"Dify Allows Unauthorized APP Enable/Disable via API","id":"CVE-2025-32796"},"products":["conda-build"],"published":"2025-06-16","related":[{"cvss_score":8.2,"headline":"Conda-build Allows Arbitrary Code Execution via Malicious Recipe Selectors","id":"CVE-2025-32798","kev_date_added":null,"published":"2025-06-16"},{"cvss_score":7.2,"headline":"Supply chain in conda-build","id":"CVE-2025-32800","kev_date_added":null,"published":"2025-06-16"},{"cvss_score":5.6,"headline":"Conda-build Vulnerable to Path Traversal via Malicious Tar File","id":"CVE-2025-32799","kev_date_added":null,"published":"2025-06-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["conda"]},"summary":"Attackers with local access can exploit a race condition in conda-build to overwrite build scripts, enabling arbitrary code execution and privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-32797/"}