CVE-2024-39925: Infoleak
An issue was discovered in Vaultwarden (formerly BitwardenRS) 1.30.3. It lacks an offboarding process for members who leave an organization. As a result, the shared organization key is not rotated when a member departs. Consequently, the departing member, whose access should be revoked, retains a copy of the organization key. Additionally, the application fails to adequately protect some encrypted data stored on the server. Consequently, an authenticated user could gain unauthorized access to encrypted data of any organization, even if the user is not a member of the targeted organization. However, the user would need to know the corresponding organizationId. Hence, if a user (whose access to an organization has been revoked) already possesses the organization key, that user could use the key to decrypt the leaked data.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-39925?
CVE-2024-39925 is classified as a medium severity vulnerability due to the potential for unauthorized access to sensitive organizational data.
How do I fix CVE-2024-39925?
To resolve CVE-2024-39925, ensure that an offboarding process is implemented to immediately revoke access and rotate the shared organization key when a member leaves.
Which versions of Vaultwarden are affected by CVE-2024-39925?
CVE-2024-39925 affects Vaultwarden versions prior to 1.32.0, specifically noted in version 1.30.3.
What impact does CVE-2024-39925 have on organizations?
CVE-2024-39925 allows departing members to retain access to the organizational vault, potentially compromising sensitive information.
Is there a patch available for CVE-2024-39925?
Yes, the vulnerability was addressed in Vaultwarden version 1.32.0, which includes the necessary fixes.