this post was submitted on 22 Nov 2024
58 points (98.3% liked)

Selfhosted

61978 readers
1112 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years 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 22 points 2 years 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 2 years 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 2 years ago

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

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

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

[–] Branquinho@lemmy.eco.br 4 points 2 years ago

Correct. Only users without 2fa were in danger.