Code repository hosting service GitHub announced that it has paid out more than $1.5 million through its bug bounty program since 2016.
Code repository hosting service GitHub announced that it has paid $524,250 through its bug bounty program for 203 vulnerabilities affecting its products and services in 2020. The company revealed that it paid more than $1.5 million since 2016.
“2020 was our busiest year yet. From February 2020 to February 2021, we handled a higher volume of submissions than any previous year. We’re proud that we’ve kept our time to first reply, triage, and payout for submissions within our aggressive standards as the program has grown.” states the Microsoft-owned company.
The company managed 1,066 submissions across its public and private programs.
GitHub proudly claimed that its response times were improved by 4 hours compared to 2019, in 2020 the average was 13 hours to the first response.
The GitHub bug bounty program was ranked as one of the top programs on HackerOne!
According to the company, submissions were validated and triaged internally to partner teams within 24 hours on average and bounties were paid out on average 24 days after the submission of an eligible report.
GitHub announcement also includes technical details about a rare Universal open redirect issue on GitHub.com that was submitted in 2020. The vulnerability was reported by William Bowling, an attacker could have exploited it to log into GitHub Gist for any user by tricking them into clicking a specially crafted link. Bowling was awarded $10,000 for this flaw.
“2021 has seen significant investment and growth across GitHub’s security program. In June, we created a new internal team dedicated to the execution and growth of our bug bounty program,” continues the post. “This team will help further accelerate and refine our triage and response process as well as expand into new initiatives such as live hacking events and additional private bug bounty programs.”
In 2020 GitHub became a CVE Number Authority (CNA) with MITRE and we began issuing CVEs for vulnerabilities in GitHub Enterprise Server.
Follow me on Twitter: @securityaffairs and Facebook
| [adrotate banner=”9″] | [adrotate banner=”12″] |
(SecurityAffairs – hacking, CVE)
[adrotate banner=”5″]
[adrotate banner=”13″]
