Skip to content

Instantly share code, notes, and snippets.

@pryorda
pryorda / notes.md
Last active December 6, 2024 06:22
kubectl notes

kubectl run tested-pod --rm -it --image=busybox:latest --restart=Never
--overrides=' {"spec": { "containers": [ { "name":"tested-pod", "image":"busybox:latest", "stdin":true, "tty":true, "securityContext": {

@pryorda
pryorda / github_bugbountyhunting.md
Created December 6, 2024 06:26 — forked from EdOverflow/github_bugbountyhunting.md
My tips for finding security issues in GitHub projects.

GitHub for Bug Bounty Hunters

GitHub repositories can disclose all sorts of potentially valuable information for bug bounty hunters. The targets do not always have to be open source for there to be issues. Organization members and their open source projects can sometimes accidentally expose information that could be used against the target company. in this article I will give you a brief overview that should help you get started targeting GitHub repositories for vulnerabilities and for general recon.

Mass Cloning

You can just do your research on github.com, but I would suggest cloning all the target's repositories so that you can run your tests locally. I would highly recommend @mazen160's GitHubCloner. Just run the script and you should be good to go.

$ python githubcloner.py --org organization -o /tmp/output