4 ms·
Federal frenzy to patch gaping Gitlab account takeover hole
- treflop 3y agoMy god I read up a little on the vulnerability and it might have been written as a feature to recover your account with any email address?? The module was called RecoverableByAnyEmail or something.
- thedanbob 3y agoThe intention was "any email associated with the user". You submitted an email address, Gitlab looked up the account associated with it, then sent the reset email to the supplied address. The issue was they didn't consider what would happen if you submitted an array of emails.
- deng 3y agoHa, I thought this is about the latest account takeover vulnerability when using Bitbucket OAuth (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4024 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-4024), but it's actually still about the old one from January...
- TheRealDunkirk 3y agoNot to worry. My company is still on version 15. We stay BEHIND the curve, where it's SAFE.
- deleted 3y ago[deleted]
- lcnPylGDnU4H9OF 3y agoGotta avoid those supply-chain vulnerabilities.
- pdevr 3y agoThe way releases are done and security is handled, one can argue that it makes sense to stay one major version behind - as long as it is a version to which security patches are applied regularly.
- pjmorris 3y agoMy mid-90's boss often repeated his old bosses' sayin "No oh," as in never depend on an initial release, wait for the patches.
- deng 3y agoGitLab only supports the latest three point releases, so that's not an option here.
- alephnerd 3y ago> it makes sense to stay one major version behind - as long as it is a version to which security patches are applied regularly That's why companies offer LTS SKUs.
- gottorf 3y agoI follow this rule, or the variant where you wait for the first point release of a new major version, wherever possible. My desktop ran Debian bullseye until maybe about a month ago, when I updated to bookworm on its 5th point release. My browser of choice on that machine is firefox-esr, which is still on the 115.x branch.
- louky 3y agoI'm updating to bookworm on my daily driver laptop today - testing the full system backup now. I've had minimal issues recently with debian but decades of debacles (not just debian, everything from RSX-11 to windows server) have made me cautious. So exhausted with wasted time.
- wtf_is_up 3y agoI've really come to enjoy Debian stable. It's going to take something significant to get me off Bookworm.
- metaphor 3y ago> The upshot of all this is that admins who enabled some form of two-factor authentication (2FA) in GitLab are safe and unaffected by the vulnerability. And of course you enabled 2FA, didn't you? ...which begs the question: What US federal agencies aren't deploying their GitLab instances behind CAC auth at a minimum?
- codeslave13 3y agoYou would be very very surprised how many federal agencies still use just a pw for vpn etc access to their whole network. Or maybe you wouldn’t.
- mugsie 3y agoBasically all of them? Even the DOD Iron bank / repo1 has non CAC modes behind an auth provider. They have forced 2FA on from what I can see now though