The LastPass hack was caused by a Sr. DevOPs not practicing secure OPs at home (was running a very old version of Plex). It didn’t attack the technology stack itself, it attacked one of the employees. User passwords were encrypted, so attackers would need to break that encryption to access stored passwords.
You missed the Okta breach, which impacted support customers, but also didn’t expose stored passwords.
Bitwarden hasn’t been hacked, and the closest I’ve heard of is this security research, but that’s using a feature that’s disabled by default, requires using a keyboard shortcut, and doesn’t work on all sites anyway. Yet they patched very quickly anyway.
I personally trust Bitwarden. They have acted professionally at every turn, and I can self-host if I choose. I don’t trust LastPass or Okta (though I need to use Okta for work), and I don’t particularly trust 1password despite them not being breached because their product is not FOSS. Chrome is a big product with lots of breaches every day, so I’d really prefer to not have my passwords stored by the same software stack as a massive hacking target. Bitwarden has separate desktop apps, so I can completely separate my data if I so choose.
My point was - no tech giant leaked passwords but small guys did. We have no insight into how internal policies look like and if they are actually followed, we can only see outcomes. Lastpass exposed encrypted passwords in 2022. In 2019 1Password app had a bug where it didn’t clear master password after logoff and kept it in plaintext. Both enormous yikes for companies that deal primarily in security.
Yes, that’s bad, but attackers would still need to break the encryption. Nobody does that, except maybe state level actors, and if you’re worried about that, you wouldn’t use commodity password managers.
1Password app had a bug where it didn’t clear master password after logof
On the negative side, the master password remains in memory when unlocked (albeit in obfuscated form) and the software fails to scrub the obfuscated password memory region sufficiently when transitioning from the unlocked to the locked state. We also found a bug where, under certain user actions, the master password can be left in memory in cleartext even while locked.
To exploit this, the attacker would need access to the memory of the device and know how to find the password in memory. It’s certainly not ideal, but it’s also not very exploitable.
The newer version is worse in this regard, but it still requires that relatively advanced exploit.
In the conclusion:
However, each password manager fails in implementing proper secrets sanitization for various reasons.
This isn’t unique to 1Password, it’s probably common across password managers. Unfortunately BitWarden wasn’t part of this research because I’m interested to know how it fairs here.
That said, I don’t use or recommend either LastPass or 1Password because they’re not FOSS, I just don’t like FUD. I use and recommend Bitwarden because it’s audited, FOSS, and competitively priced.
1password did not get hacked.
The LastPass hack was caused by a Sr. DevOPs not practicing secure OPs at home (was running a very old version of Plex). It didn’t attack the technology stack itself, it attacked one of the employees. User passwords were encrypted, so attackers would need to break that encryption to access stored passwords.
You missed the Okta breach, which impacted support customers, but also didn’t expose stored passwords.
Bitwarden hasn’t been hacked, and the closest I’ve heard of is this security research, but that’s using a feature that’s disabled by default, requires using a keyboard shortcut, and doesn’t work on all sites anyway. Yet they patched very quickly anyway.
I personally trust Bitwarden. They have acted professionally at every turn, and I can self-host if I choose. I don’t trust LastPass or Okta (though I need to use Okta for work), and I don’t particularly trust 1password despite them not being breached because their product is not FOSS. Chrome is a big product with lots of breaches every day, so I’d really prefer to not have my passwords stored by the same software stack as a massive hacking target. Bitwarden has separate desktop apps, so I can completely separate my data if I so choose.
That’s a lot of words to confirm what I said.
Here are fewer words: 1password didn’t get hacked (you claimed they did), LastPass didn’t expose user passwords.
I would still rather use Bitwarden over them though. Definitely not Google though, (I don’t even have a google account if I wanted to)
I’m the same way, I use Bitwarden myself.
My point was - no tech giant leaked passwords but small guys did. We have no insight into how internal policies look like and if they are actually followed, we can only see outcomes. Lastpass exposed encrypted passwords in 2022. In 2019 1Password app had a bug where it didn’t clear master password after logoff and kept it in plaintext. Both enormous yikes for companies that deal primarily in security.
Yes, that’s bad, but attackers would still need to break the encryption. Nobody does that, except maybe state level actors, and if you’re worried about that, you wouldn’t use commodity password managers.
I think you’re talking about this study:
To exploit this, the attacker would need access to the memory of the device and know how to find the password in memory. It’s certainly not ideal, but it’s also not very exploitable.
The newer version is worse in this regard, but it still requires that relatively advanced exploit.
In the conclusion:
This isn’t unique to 1Password, it’s probably common across password managers. Unfortunately BitWarden wasn’t part of this research because I’m interested to know how it fairs here.
That said, I don’t use or recommend either LastPass or 1Password because they’re not FOSS, I just don’t like FUD. I use and recommend Bitwarden because it’s audited, FOSS, and competitively priced.