XWiki up to 12.10.9/13.4.3 WAR xwiki.cfg authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in XWiki up to 12.10.9/13.4.3. Impacted is an unknown function of the file xwiki.cfg of the component WAR. Performing a manipulation results in authorization. This vulnerability is identified as CVE-2022-23621. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in XWiki up to 12.10.9/13.4.3 (Content Management System). This affects some unknown processing of the file xwiki.cfg of the component WAR. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 02/10/2022 as GHSA-2jhm-qp48-hv5j. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-23621 since 01/19/2022. Technical details are known, but no exploit is available.
Upgrading to version 12.10.9, 13.4.3 or 13.7-rc1 eliminates this vulnerability. Applying the patch df8bd49b5a4d87a427002c6535fb5b1746ff117a 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.1
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.5
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: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
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 12.10.9/13.4.3/13.7-rc1
Patch: df8bd49b5a4d87a427002c6535fb5b1746ff117a
Timeline
01/19/2022 🔍02/10/2022 🔍
02/10/2022 🔍
02/13/2022 🔍
Sources
Advisory: GHSA-2jhm-qp48-hv5jStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2022-23621 (🔍)
GCVE (CVE): GCVE-0-2022-23621
GCVE (VulDB): GCVE-100-192681
Entry
Created: 02/10/2022 10:43Updated: 02/13/2022 11:13
Changes: 02/10/2022 10:43 (52), 02/13/2022 11:13 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.