Justin Garrick justingarrick

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

I have found that Adobe services still worked fine after doing this, but your milage may vary, so be sure to have a back-up of your original install media or whatever.

You may or may not have these services, you can lookup what is running on your machine with launchctl list |grep -i adobe also run with sudo to find what is running at higher privledges.

User Level

Stop Services

launchctl stop com.adobe.acc.AdobeDesktopService.2252.965FE800-C621-41D6-898D-821201FB2F8A

	private static OkHttpClient getUnsafeOkHttpClient() {
	try {
	// Create a trust manager that does not validate certificate chains
	final TrustManager[] trustAllCerts = new TrustManager[]{
	new X509TrustManager() {
	@Override
	public void checkClientTrusted(java.security.cert.X509Certificate[] chain,
	String authType) throws CertificateException {
	}