Vulnerability Disclosure: Authentication Bypass in Vaultwarden versions < 1.32.5 (insinuator.net)
from Branquinho@lemmy.eco.br to selfhosted@lemmy.world on 22 Nov 2024 12:49
https://lemmy.eco.br/post/8986904

Please update Vaultwarden as soon as possible if you did not do it yet.

#selfhosted

threaded - newest

cron@feddit.org on 22 Nov 2024 12:59 next collapse

The blog post contains an interesting tineline. Apparently, the first fix was not sufficient. So if you have updated Vaultwaren before November 18, update it again.

Copy of the timeline:

  • End of October 2024: ERNW assesses Vaultwarden for the customer.
  • November 08, 2024: ERNW discloses the vulnerabilities to the Vaultwarden team.
  • November 10, 2024: Fix and release of Vaultwarden v1.32.4.
  • November 11, 2024: ERNW retests the software and identifies that the fix is not sufficient.
  • November 11, 2024: Public merge with fix and request for feedback by the Vaultwarden team.
  • November 12, 2024: ERNW acknowledges that the fix is complete.
  • November 18, 2024: Release of Vaultwarden v1.32.5.
zako@piefed.social on 22 Nov 2024 13:19 next collapse

Hopefully, it was previously announced to update as soon as possible before disclosing the vulnerabilty. Good job by security experts and Vaultwarden team!

neshura@bookwormstory.social on 22 Nov 2024 14:01 collapse

Yes it was, the release notes explicitly specify it for 1.32.4 and 1.32.5

brownmustardminion@lemmy.ml on 22 Nov 2024 16:25 collapse

Am I understanding correctly that if users had 2FA, the vulnerability would be prevented from gaining access?

Branquinho@lemmy.eco.br on 22 Nov 17:15 collapse

Correct. Only users without 2fa were in danger.