We got admin access to Baseten's production GitHub
summary
The authors used their autonomous hacking agent, Strix, to test the security of Baseten before using their services, discovering a critical vulnerability in an old container image. Strix autonomously identified a public Harbor registry, pulled an image, and extracted a live GitHub personal access token from the image's build history. This token granted admin and push access to Baseten's core product and deployment repositories. The incident demonstrates how outdated build artifacts and overly permissive tokens can create severe security holes that AI-driven tools can exploit rapidly.
key points
- A GitHub token was leaked through a Docker build argument (ARG), which saved the credential directly into the image's metadata and build history rather than keeping it temporary.
- The leaked token had excessive permissions, providing admin access to multiple private repositories including the main product and GitOps repos, rather than being limited to read-only access for specific dependencies.
- Strix demonstrated the ability to perform full-chain reconnaissance and exploitation autonomously, moving from host enumeration to credential extraction and permission verification in 25 minutes.
who should read it
DevOps engineers and security professionals who manage containerized builds and use GitHub for dependency management.
discussion mixed
consensus
Commenters generally agree that Baseten's prompt communication and rapid remediation of the critical vulnerability were commendable. However, a significant divide exists regarding the reward; some argue that a $13B company should provide financial compensation instead of mere swag, while others contend that since the discovery occurred during a B2B security audit by a potential customer, monetary rewards are inappropriate or unnecessary. The sentiment leans toward the belief that rewarding good-faith researchers is vital to prevent them from selling vulnerabilities to malicious actors.
top insight
The discussion highlights a fundamental tension between the nature of the discovery—a B2B security review during a procurement process—and the general ethics of bug bounties. While some view the report as a professional service inherent to a business relationship, others argue that the severity of the bug (admin escalation in GitHub) transcends the context and warrants a financial payout to incentivize honest disclosure over monetization on the dark web.
Generated by an LLM from the article and thread. Check the sources before relying on it.