Holes in Your Bitbucket: Why Your CI/CD Pipeline Is Leaking Secrets
Bitbucket Secured Variables leak secrets via artifact objects; recommendations include using dedicated secrets managers and code scanning.
- from
- CI/CD Attacks
- added
- 2026-10-10
- likes
- 0
similar
-
10 real-world stories of how we've compromised CI/CD pipelines nccgroup.com
Examples include exploiting S3 misconfigurations, Jenkins plugin flaws, GitLab runner privilege escalations, Kubernetes pod annotation vulnerabilities, and compromised developer laptops.
-
How I hacked into Google's internal corporate assets observationsinsecurity.com
More ways to find dependencies in code for Dependency Confusion.
-
Git Secrets github.com
Amazon AWS - Scan git repositories for secrets committed within code or commit messages.
-
GitLab Secrets github.com
A tool that can reveal deleted GitLab commits that potentially contain sensitive information and are not accessible via the public Git history.
-
How We Discovered Vulnerabilities in CI/CD Pipelines of Popular Open-Source Projects cycode.com
Extracting all repository and organization secrets in GitHub Actions.
-
bitbuckets bitbucket.org
Git and Mercurial repository hosting.
CI/CD Attacks › Techniques > Publicly Exposed Sensitive Data: “Bitbucket Secured Variables leak secrets via artifact objects; recommendations include using dedicated secrets managers and code scanning.”