CVE-2022-29161: Crypto script service uses hashing algorithm SHA1 with RSA for certificate signature in xwiki-platform

Published May 5, 2022
·
Updated

Impact XWiki Crypto API will generate X509 certificates signed by default using SHA1 with RSA, which is not considered safe anymore for use in certificate signatures, due to the risk of collisions with SHA1. Note that this API is never used in XWiki Standard but it might be used in some extensions of XWiki.

Patches The problem has been patched in XWiki version 13.10.6, 14.3.1 and 14.4-rc-1. Since then, the Crypto API will generate X509 certificates signed by default using SHA256 with RSA.

Workarounds Administrators are advised to upgrade their XWiki installation to one of the patched versions. If the upgrade is not possible, it is possible to patch the module xwiki-platform-crypto in a local installation by applying the change exposed in https://github.com/xwiki/xwiki-platform/commit/26728f3f23658288683667a5182a916c7ecefc52 and re-compiling the module.

References https://jira.xwiki.org/browse/XWIKI-19676 https://github.com/openssl/openssl/blob/master/CHANGES.md?plain=1#L938 https://github.com/openssl/openssl/issues/16650

For more information If you have any questions or comments about this advisory: Open an issue in Jira XWiki Email us at security ML

Other sources

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. The XWiki Crypto API will generate X509 certificates signed by default using SHA1 with RSA, which is not considered safe anymore for use in certificate signatures, due to the risk of collisions with SHA1. The problem has been patched in XWiki version 13.10.6, 14.3.1 and 14.4-rc-1. Since then, the Crypto API will generate X509 certificates signed by default using SHA256 with RSA. Administrators are advised to upgrade their XWiki installation to one of the patched versions. If the upgrade is not possible, it is possible to patch the module xwiki-platform-crypto in a local installation by applying the change exposed in 26728f3 and re-compiling the module.

Affected Software

4 affected componentsFixes available
maven/org.xwiki.platform:xwiki-platform-crypto>=14.0.0<14.3.1
14.3.1
maven/org.xwiki.platform:xwiki-platform-crypto<13.10.6
13.10.6
XWiki xwiki<13.10.6
XWiki xwiki>=14.0<14.3.1

Event History

May 5, 2022
CVE Published
via MITRE·11:35 PM
Data Sourced
via MITRE·11:35 PM
DescriptionSeverityWeakness
May 24, 2022
Advisory Published
12:47 PM

Frequently Asked Questions

1

What is the severity of CVE-2022-29161?

CVE-2022-29161 is considered a moderate severity vulnerability due to the risk of SHA1 collision attacks in certificate signatures.

2

How do I fix CVE-2022-29161?

To fix CVE-2022-29161, upgrade to XWiki Crypto API version 14.3.1 or 13.10.6.

3

Which versions of XWiki are affected by CVE-2022-29161?

CVE-2022-29161 affects XWiki versions from 14.0 to 14.3.1 and 13.10.6 and earlier.

4

What impact does CVE-2022-29161 have on XWiki?

CVE-2022-29161 can lead to insecure certificate signatures, making them vulnerable to forgery.

5

Is CVE-2022-29161 used in XWiki Standard?

CVE-2022-29161 is not used in XWiki Standard but could affect custom implementations of the XWiki Crypto API.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203