CVE-2022-41933: Plaintext storage of password in org.xwiki.platform:xwiki-platform-security-authentication-default
XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. When the reset a forgotten password feature of XWiki was used, the password was then stored in plain text in database. This only concerns XWiki 13.1RC1 and newer versions. Note that it only concerns the reset password feature available from the "Forgot your password" link in the login view: the features allowing a user to change their password, or for an admin to change a user password are not impacted. This vulnerability is particularly dangerous in combination with other vulnerabilities allowing to perform data leak of personal data from users, such as GHSA-599v-w48h-rjrm. Note that this vulnerability only concerns the users of the main wiki: in case of farms, the users registered on subwiki are not impacted thanks to a bug we discovered when investigating this. The problem has been patched in version 14.6RC1, 14.4.3 and 13.10.8. The patch involves a migration of the impacted users as well as the history of the page, to ensure no password remains in plain text in the database. This migration also involves to inform the users about the possible disclosure of their passwords: by default, two emails are automatically sent to the impacted users. A first email to inform about the possibility that their password have been leaked, and a second email using the reset password feature to ask them to set a new password. It's also possible for administrators to set some properties for the migration: it's possible to decide if the user password should be reset (default) or if the passwords should be kept but only hashed. Note that in the first option, the users won't be able to login anymore until they set a new password if they were impacted. Note that in both options, mails will be sent to users to inform them and encourage them to change their passwords.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
XWiki Platform security authentication default (org.xwiki.platform:xwiki-platform-security-authentication-default)to a version that resolves this vulnerability.Fixed in 14.6RC1 - Upgrade
Upgrade
XWiki Platform security authentication default (org.xwiki.platform:xwiki-platform-security-authentication-default)to a version that resolves this vulnerability.Fixed in 14.4.3 - Upgrade
Upgrade
XWiki Platform security authentication default (org.xwiki.platform:xwiki-platform-security-authentication-default)to a version that resolves this vulnerability.Fixed in 13.10.8 - Configuration
During the required migration, use the administrator option to reset the users' passwords (default behavior) for impacted main-wiki users.
XWiki reset a forgotten password migration reset password on migration (administrator property) = default: reset impacted users' passwords (and send two emails) - Configuration
Alternatively, during the required migration, set the administrator option to keep existing passwords but store them only as hashes for impacted main-wiki users.
XWiki reset a forgotten password migration reset password on migration (administrator property) = keep passwords but only hashed - Compensating control
Ensure the migration/informational emails are applied only to users of the main wiki; do not apply the impacted-user migration to subwiki farm users because subwiki users are stated as not impacted.
Event History
Frequently Asked Questions
What is the severity of CVE-2022-41933?
CVE-2022-41933 is considered to be a high severity vulnerability due to the exposure of sensitive user passwords.
How do I fix CVE-2022-41933?
To fix CVE-2022-41933, you should update your XWiki installation to a version that is not affected, specifically versions post 14.4.3.
Which versions of XWiki are affected by CVE-2022-41933?
CVE-2022-41933 affects XWiki versions from 13.1-RC1 up to but not including 14.4.3.
What impact does CVE-2022-41933 have on password security?
CVE-2022-41933 impacts password security by storing passwords in plain text, making them vulnerable to unauthorized access.
Is there a workaround for CVE-2022-41933 until I can update?
A workaround for CVE-2022-41933 is to disable the password reset feature, minimizing the risk of plain text storage until you can perform the update.