I am mostly impressed that they paid out $25k in under a week. That’s a sign of not just a good engineering setup, but some good bureaucracy as well.
Been managing GHE for years, and I have been consistently impressed with Github's code quality, competence, and even product management (nearly every time I think, "there should be a way to...", there already is).
From the outside, at least, they look like the model to emulate for this sort of application.
(I have come to think, as a software engineer, that we've comuterized so much of social life such that our economy literally could not afford it if it wasn't mostly crap).
And this was definitely approved before they went out and told people what they would pay for different bugs.
Your sentiment, though, is why it's nice when it is publicized that the system is working as intended, like it did in this case.
* 2019-06-19 23:36:50 UTC Issue confirmed by GitHub security team
* 2019-06-20 02:44:29 UTC Issue patched on github.com, GitHub replies on HackerOne to double-check that the patch fully resolves the issue
* 2019-06-26 16:19:20 UTC GitHub Enterprise 2.17.3, 2.16.12, 2.15.17, and 2.14.24 released with the patch (see GitHub’s announcement).
* 2019-06-26 22:30:45 UTC GitHub awards $25000 bounty
So used to these disclosure articles where the timelines look very different, communication is lacking and there's pushback on the bounties etc.
Refreshing to see that sometimes the process works as everyone hopes it will.