3 ms·
Our forgejo instance got affected by this. I saw the news and thought we don't need to upgrade (yet), as registration is closed for new users, and users having
by mrnaif 2mo ago
Our forgejo instance got affected by this. I saw the news and thought we don't need to upgrade (yet), as registration is closed for new users, and users having access is only those we control.
As it turns out, when in app.ini we have DISABLE_REGISTRATION = true, it doesn't actually disable registration...
Even though no sign in or sign up form was rendered, the attacker used openid registration
as in our config I had
[openid]
ENABLE_OPENID_SIGNIN = true
ENABLE_OPENID_SIGNUP = true
attacker created a fake openid server, registered this way, created like 100+ repositories, was able to create a superadmin account on forgejo, mint tokens, execute commands from the runner trying to escalate permissions - either via git hooks, or in runner itself. Luckily our runner was running on a separate isolated server, but potential damage could have been much worse.
So yeah, everyone update ASAP if you don't want to spend half a day fixing the consequences (: