PRODSEC-4321: [supply-chain] Replace third-party URLs with Artifactory#2868
Conversation
|
All contributors have signed the CLA ✍️ ✅ |
|
Hi! 👋 The Security Foundation team is replacing third-party URLs with Snowflake Artifactory according to our company's security policies. This change ensures all dependencies are fetched through our controlled proxy rather than directly from public registries. @sfc-gh-turbaszek @sfc-gh-akolodziejczyk — could you please review this PR? If you were chosen incorrectly, please add the appropriate person for reviewing it. If you have any questions regarding this PR, please reach out on Slack to Jowita Drozdowicz. Thank you! |
Revert Artifactory URLs in Dockerfiles and CI scripts that are used by GitHub Actions, where the internal Artifactory is unreachable. Restore JENKINS_HOME conditional for wiremock downloads so Jenkins uses Artifactory while GHA uses public Maven/GitHub URLs. Files kept with Artifactory (Jenkins-only): test_darwin.sh, test_windows.bat, prober/Dockerfile. Co-authored-by: Cursor <cursoragent@cursor.com>
Add DESCRIPTION.md entry for the supply-chain URL replacement to satisfy the check_change_log CI gate. Co-authored-by: Cursor <cursoragent@cursor.com>
Summary
Following the recent axios supply-chain attack, the Product Security Team is working to eliminate dependencies on third-party package sources and ensure all packages are downloaded through Snowflake Artifactory. This reduces the risk of compromised upstream packages reaching our build and runtime environments.
Changes
Why
Pulling packages directly from public registries (PyPI, PyTorch, Go module proxy) bypasses our artifact scanning and caching layer. If an attacker compromises an upstream package - as happened with axios - the malicious version would be fetched directly into our environments. Routing through Artifactory gives us a controlled checkpoint for vulnerability scanning and version caching.