this post was submitted on 22 Nov 2024
50 points (100.0% liked)

Selfhosted

40329 readers
638 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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

top 5 comments
sorted by: hot top controversial new old
[–] cron@feddit.org 15 points 1 day ago

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 7 points 1 day ago (1 children)

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 5 points 1 day ago

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

[–] brownmustardminion@lemmy.ml 2 points 1 day ago (1 children)

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

[–] Branquinho@lemmy.eco.br 3 points 1 day ago

Correct. Only users without 2fa were in danger.