Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Given it existed for 5 days and you’re only now finding out about it, it sounds to me like it was perhaps a bug that was fixed without realising the full impact of it, or perhaps without realising it made it to production; and only an audit that happened later caught it.

Not ideal by any means. I’d be curious to know if my theory is correct or not.



Their statements indicate they were aware and investigating. My frustration is that they didn't give users the opportunity to do their own timely investigation.

> GitHub learned via a customer support ticket that GitHub Apps were able to generate scoped installation tokens with elevated permissions. Each of these tokens are valid for up to 1 hour.

> GitHub quickly fixed the issue and established that this bug was recently introduced, existing for approximately 5 days between 2022-02-25 18:28 UTC and 2022-03-02 20:47 UTC.

> GitHub immediately began working to fix the bug and started an investigation into the potential impact. However due to the scale and complexity of GitHub Apps and their short-lived tokens, we were unable to determine whether this bug was ever exploited.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: