this post was submitted on 19 May 2023
20 points (100.0% liked)

Technology

37727 readers
721 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

The vulnerability affects the KeePass 2.X branch for Windows, and possibly for Linux and macOS. It has been fixed in the test versions of KeePass v2.54 – the official release is expected by July 2023. It’s unfortunate that the PoC tool is already publicly available and the release of the new version so far off, but the risk of CVE-2023-32784 being abused in the wild is likely to be pretty low, according to the researcher.

you are viewing a single comment's thread
view the rest of the comments
[–] admin@beehaw.org 3 points 2 years ago (29 children)
[–] sxan@midwest.social 12 points 2 years ago (25 children)

No.

Tge real answer is not to give control of your passwords to a third party; it's to not use crappy .Net programs.

KeePassXC is not affected.

[–] admin@beehaw.org 4 points 2 years ago (5 children)

KeePassXC could be another viable choice. Bitwarden has been free of any incidents for the eight years that I've been using it.

[–] rysiek@szmer.info 9 points 2 years ago

Bitwarden is also FLOSS and self-hostable. As much as I love KeePassXC, using it for team passwords is a pain. Having a self-hosted Bitwarden thingy would be way better.

load more comments (4 replies)
load more comments (23 replies)
load more comments (26 replies)