25 Vulnerabilities Found in Cloud Password Managers


Researchers from ETH Zurich discovered 25 serious vulnerabilities in Bitwarden, LastPass, and Dashlane cloud password managers. These flaws let malicious servers bypass zero-knowledge encryption claims to access, modify, or recover user vaults. The three services protect over 60 million users worldwide.

The attacks work under a malicious server model where cloud infrastructure deviates from protocols. Despite vendor claims of end-to-end encryption, servers can compromise confidentiality and integrity. ETH disclosed findings responsibly to all three vendors.

Bitwarden faced 12 attacks, LastPass 7, and Dashlane 6. Issues span key escrow flaws, item encryption weaknesses, sharing exploits, and legacy compatibility bugs. Many require just one user interaction like a login or sync.

ETH Zurich Research Details

ETH researchers tested client-server interactions against fully compromised servers. They found zero-knowledge protections fail across recovery, sharing, and encryption layers. Full technical paper available through university channels.

Vendors received coordinated disclosure. Bitwarden got notice January 27, 2025. LastPass on June 4, 2025. Dashlane on August 29, 2025. All followed 90-day remediation windows. ETH announcement

Attack Categories Breakdown

Key Escrow Attacks: Recovery and SSO flaws enable unauthenticated key substitution. Attackers rotate or convert keys during organization joins or dialogs.

Item-Level Encryption Flaws: Missing authentication, key separation, and weak ciphers leak metadata, enable field swaps, and remove brute-force protections.

Sharing Exploits: Public keys lack authentication. Attackers inject organization members or overwrite shared vault keys on join.

Backwards Compatibility: Legacy AES-CBC support triggers downgrades. Protection mechanisms disable after syncs or logins.

Complete Vulnerability Table

Attack RefProductRoot CauseImpactClient Interactions
BW01BitwardenNo Key Auth, Key SubstitutionFull vault compromise1 join
BW02BitwardenKey SubstitutionFull vault compromise1 rotation
BW03BitwardenNo Key Auth, Key SubstitutionFull vault compromise1 dialog
LP01LastPassNo Key AuthFull vault compromise1 login
BW04BitwardenNo Auth EncRead/modify metadata
BW05BitwardenNo Key SeparationField/item swapping
BW06BitwardenNo Key SeparationLoss of confidentiality1 open
BW07BitwardenNo Auth EncNo brute-force protection1 login
LP02LastPassNo Auth EncField/item swapping
LP03LastPassNo Key SeparationLoss of confidentiality1 open
LP04LastPassNo Auth EncNo brute-force protection1 login
LP05LastPassNo Auth EncLoss of vault integrity
DL01DashlaneNo Key SeparationLoss of vault integrity
BW08BitwardenNo Key AuthAdd users to orgs1 sync
BW09BitwardenNo Key Auth, Key SubstitutionOrg compromise1 join
LP07LastPassNo Key AuthShared vault compromise1 join
DL02DashlaneNo Key AuthShared vault compromise1 join
BW10BitwardenNo Auth EncDowngrade key hierarchy
BW11BitwardenCBC SupportLoss of confidentiality2 logins
BW12BitwardenCBC SupportFull vault compromise2 logins
DL03DashlaneCBC SupportLoss of vault integrity104 syncs
DL04DashlaneCBC SupportNo brute-force protection104 syncs
DL05DashlaneCBC SupportLoss of confidentiality105 syncs
DL06DashlaneCBC SupportNo brute-force protection104 syncs
LP06LastPassNo Auth EncRead/modify metadata

Vendor Response Status

Bitwarden fixed multiple issues including minimum KDF iterations and CBC removal. LastPass addressed LP03 vault confidentiality. Dashlane released extension 6.2544.1 patching CBC flaws.

Self-hosted deployments remain at risk if servers compromise. Cloud users protected by vendor patches.

Technical Attack Examples

BW01 Malicious Auto-Enrollment: Unauthenticated organization public keys substitute victim keys during joins. Single interaction compromises entire vault.

BW06 Icon Decryption: Client requests decrypt unprotected icon URLs, leaking passwords indirectly through metadata.

BW07 KDF Downgrade: Attackers remove PBKDF2 iterations, enabling 300,000x faster brute-force attacks.

DL01 Transaction Replay: Shared keys across transactions violate integrity. Attackers replay modified transactions indefinitely.

Researchers propose four fixes for password manager protocols:

  • Authenticated Encryption (AE): Protect all ciphertext with integrity checks
  • Full Key Separation (KS): Isolate encryption keys per field/item
  • Public Key Authentication (PKA): Validate all public keys before use
  • Ciphertext Signing (SC): Sign vault contents end-to-end

Users should update all clients immediately. Enable per-item encryption where available. Monitor vendor security bulletins closely.

Impact Scale

VendorVulnerabilitiesMarket ShareUsers Affected
Bitwarden12High growth10M+
LastPass7Enterprise30M+
Dashlane6Premium20M+
Total25Dominant60M+

FAQ

Which password managers had vulnerabilities?

Bitwarden (12), LastPass (7), Dashlane (6).

What do attacks enable?

Full vault access, modification, key recovery via malicious servers.

Are patches available?

Yes. Bitwarden: KDF/CBC fixes. LastPass: LP03. Dashlane: v6.2544.1.

Do self-hosted versions fix?

No. Server compromise still works despite client updates.

What mitigations needed?

AE, KS, PKA, SC protocols per ETH researchers.

How many interactions for attacks?

Many need 1 login/sync. Worst case: 105 syncs (DL05).

Readers help support VPNCentral. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help VPNCentral sustain the editorial team Read more

User forum

0 messages