XWiki Platform prior 13.10.6/14.3.1/14.4-rc1 x509 Certificate risky encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in XWiki Platform and classified as problematic. This issue affects some unknown processing of the component x509 Certificate Handler. The manipulation leads to risky encryption. This vulnerability is documented as CVE-2022-29161. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, has been found in XWiki Platform (Content Management System). This issue affects an unknown part of the component x509 Certificate Handler. The manipulation with an unknown input leads to a risky encryption vulnerability. Using CWE to declare the problem leads to CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. Impacted is confidentiality, integrity, and availability.
The weakness was released 05/06/2022 as GHSA-h8v5-p258-pqf4. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-29161 since 04/13/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
Upgrading to version 13.10.6, 14.3.1 or 14.4-rc1 eliminates this vulnerability. Applying the patch 26728f3f23658288683667a5182a916c7ecefc52 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Risky encryptionCWE: CWE-327 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: XWiki Platform 13.10.6/14.3.1/14.4-rc1
Patch: 26728f3f23658288683667a5182a916c7ecefc52
Timeline
04/13/2022 🔍05/06/2022 🔍
05/06/2022 🔍
05/08/2022 🔍
Sources
Advisory: GHSA-h8v5-p258-pqf4Status: Confirmed
CVE: CVE-2022-29161 (🔍)
GCVE (CVE): GCVE-0-2022-29161
GCVE (VulDB): GCVE-100-199181
Entry
Created: 05/06/2022 11:44Updated: 05/08/2022 17:17
Changes: 05/06/2022 11:44 (51), 05/08/2022 17:17 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.