Summary
Use of a Broken or Risky Cryptographic Algorithm in XWiki Crypto API
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
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.
The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.
CVE-2022-29161 has a CVSS score of 5.4 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (13.10.6, 14.3.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is CVE-2022-29161? CVE-2022-29161 is a medium-severity use of a broken or risky cryptographic algorithm vulnerability in org.xwiki.platform:xwiki-platform-crypto (maven), affecting versions < 13.10.6. It is fixed in 13.10.6, 14.3.1. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
- How severe is CVE-2022-29161? CVE-2022-29161 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.xwiki.platform:xwiki-platform-crypto are affected by CVE-2022-29161? org.xwiki.platform:xwiki-platform-crypto (maven) versions < 13.10.6 is affected.
- Is there a fix for CVE-2022-29161? Yes. CVE-2022-29161 is fixed in 13.10.6, 14.3.1. Upgrade to this version or later.
- Is CVE-2022-29161 exploitable, and should I be worried? Whether CVE-2022-29161 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-29161 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-29161?
- Upgrade
org.xwiki.platform:xwiki-platform-cryptoto 13.10.6 or later - Upgrade
org.xwiki.platform:xwiki-platform-cryptoto 14.3.1 or later
- Upgrade