Popular password managers fall short of “zero-knowledge” claims

All eight of the top password managers have adopted the term “zero knowledge” to describe the complex encryption system they use to protect the data vaults that users store on their servers.

New research shows that these claims aren’t true in all cases, particularly when account recovery is in place or password managers are set to share vaults or organize users into groups. The researchers reverse-engineered or closely analyzed Bitwarden, Dashlane, and LastPass and identified ways that someone with control over the server—either administrative or the result of a compromise—can, in fact, steal data and, in some cases, entire vaults. The researchers also devised other attacks that can weaken the encryption to the point that ciphertext can be converted to plaintext.

They used several techniques. Bitwarden is affected. It’s important to note most attacks assume an attacker has full control over the password manager servers.

We don’t know yet which others password managers are impacted, as they didn’t test those as deep and couldn’t disclose them.

They said they tested more, but less in depth and/or couldn’t disclose, perhaps because of an embargo.

I’m surprised that this didn’t cause a bigger stir – no matter how theoretical the scenarios are, the findings still undermine the whole premise of these encrypted password mangers. I’m considering switching from Bitwarden to KeepassXC. What do you guys think of syncing a Keepass vault with Syncthing – is it secure?

1 Like

How is this any better? I’m not too concerned about Bitwarden/Vaultwarden yet. I think their PR said they have never been breached before, so I’ll trust them until the privacy community can come up with a better solution. I’m definitely not going back to LastPass. Eff those guys!

Yeah well there’s first time for everything, right? The point of the research was to critically assess the zero-knowledge claims these firms make, and since they don’t quite hold up to scrutiny, I’d like to think a local Keepass database would be more secure from this standpoint. Would be nice to sync it to my phone somehow, but that always brings some risks with it.

1 Like

There has to be a balance between convenience and security. Maybe you can pull it off, but most people will want to be able to sync with their phones.

If you worry about the types of attack described for Bitwarden I would advise you to self host Vaultwarden.

Vaultwarden is a rust rewritten bitwarden server.

1 Like

Absolutely, I like having that feature as well :smiley:

Thanks I might look into it, but self-hosting brings up other risks. I guess there’s no perfect solution haha

I use Syncthing for this.

1 Like

Keepass + Syncthing should be secure, yes.

2 Likes

There was a bit of controversy about security when the fork was handed over to another dev but it seems like it has been sorted out.

1 Like

I had no idea it used Rust. That’s awesome. Seems like everyone is trying to rewrite their code in Rust these days.

You miss the point. End-to-End encryption is not what was compromised. And yet it did not protect these vaults. The point is the claim made by these companies that they have “Zero Knowledge” when they actually have quite a bit. Enough to compromise existing vaults. Just because these specific exploit techniques were patched against doesn’t mean others don’t exist.

The problem is the centralized server is there to be attacked, that old weak code creeps in over time and other poorly designed code features leak. Then put 20 million passwords in one place and the motivation to find the next one goes way up.

Take a look at Ink and Switch and the local-first movement.

1 Like

Why would that be a shame? Did you read the article? Its not about one being better than the other it’s about a centralized attack surface that can see and manipulate the parameters around security of the vault, there for making clear that these platforms aren’t Zero Knowledge. Maybe you can say Proton Pass doesn’t make this claim, like someone said, but then realize what you are saying… if you say this you are admitting to potential vulnerability referenced in this article.

The only true way to avoid these vulnerabilities is to use a local-first password manager. Clearly Proton Pass is not.

You can also self-host or have a solution that has no attack surface on the server.