Text of bounty.github.com › researchers › bitquark.html as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

Bitquark | GitHub Bug Bounty

3,600 pts Bitquark @bitquark Earned badges Cross-Site Scripting (XSS) Missing Function Level Access Control Security Misconfiguration Unvalidated Redirect or Forward Reported vulnerabilities 500 pts Stored XSS on render.github.com @bitquark reported a stored XSS vulnerability within GeoJSON rendering on render.github.com . While exploitation of this vulnerability was limited to a sandboxed domain, we still took the threat seriously.

We addressed the behavior by properly escaping user-controlled input. Reported on 02-08-2014 for GitHub.com 1,200 pts Content Security Policy bypass @bitquark reported a bug where we were not sending the Content Security Policy header in responses when the request included specific parameters. The CSP header is an important security feature supported by modern browsers to significantly mitigate the risk of XSS. We addressed this issue by ensuring the correct security headers are set on all responses.

Reported on 02-02-2014 for GitHub.com 400 pts Open redirect via Referer header @bitquark reported a low-risk open redirect on GitHub.com. Rails code such as redirect_to :back could be exploited to redirect a user to an arbitrary location if they were first forwarded to GitHub via a malicious site. We addressed the behavior by limiting the locations passed via Referer headers that we allow to be used for redirection. Reported on 02-02-2014 for GitHub.com 500 pts Reflected XSS on render.github.com @bitquark reported a reflected XSS vulnerability within GeoJSON rendering on render.github.com .

While exploitation of this vulnerability was limited to a sandboxed domain, we still took the threat seriously. We addressed the behavior by properly escaping user-controlled input. Reported on 02-02-2014 for GitHub.com 200 pts Organization creation self-XSS on GitHub.com @bitquark reported a reflected self-XSS vulnerability that existed within our organization creation page. If the organizaton name contained HTML markup and the submitted coupon code was invalid, the unescaped organization name was used in the response.

While this was a reflected self-XSS vulnerability that was also mitigated by our use of CSP, we still took the threat seriously. We addressed the behavior by properly escaping the organization name. In addition, we refactored the shared template logic to reduce the chance that a similar vulnerability will occur elsewhere. Reported on 02-01-2014 for GitHub.com 800 pts Organization membership disclosure @bitquark reported a bug where a page listing the members of a team could be viewed by users who were not members of the organization.

We addressed this by adding the missing authorization check on this page. Reported on 02-01-2014 for GitHub.com