Skip to content

Use of a Broken or Risky Cryptographic Algorithm in XWiki Crypto API

Moderate severity GitHub Reviewed Published May 5, 2022 in xwiki/xwiki-platform • Updated Jul 21, 2023

Package

maven org.xwiki.platform:xwiki-platform-crypto (Maven)

Affected versions

< 13.10.6
>= 14.0.0, < 14.3.1

Patched versions

13.10.6
14.3.1

Description

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 xwiki/xwiki-platform@26728f3 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
openssl/openssl#16650

For more information

If you have any questions or comments about this advisory:

References

@surli surli published to xwiki/xwiki-platform May 5, 2022
Published by the National Vulnerability Database May 6, 2022
Published to the GitHub Advisory Database May 24, 2022
Reviewed May 24, 2022
Last updated Jul 21, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

EPSS score

0.219%
(60th percentile)

Weaknesses

CVE ID

CVE-2022-29161

GHSA ID

GHSA-h8v5-p258-pqf4

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.