We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
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.
Reserved 2025-04-10 | Published 2025-06-16 | Updated 2025-06-16 | Assigner GitHub_MCWE-277: Insecure Inherited Permissions
github.com/...-build/security/advisories/GHSA-vfp6-3v8g-vcmm
github.com/conda/conda-build/pull/5
github.com/...ommit/d246e49c8f45e8033915156ee3d77769926f3c2e
github.com/...1ef1065df9e00d86ac97f087c/conda_build/build.py
Support options