dotCMS up to 22.02 ContentResource API filename pathname traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in dotCMS up to 22.02. The impacted element is an unknown function of the component ContentResource API. The manipulation of the argument filename leads to pathname traversal. This vulnerability is referenced as CVE-2022-26352. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability was found in dotCMS up to 22.02 (Content Management System) and classified as critical. This issue affects some unknown processing of the component ContentResource API. The manipulation of the argument filename with an unknown input leads to a pathname traversal vulnerability. Using CWE to declare the problem leads to CWE-21. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in the ContentResource API in dotCMS 3.0 through 22.02. Attackers can craft a multipart form request to post a file whose filename is not initially sanitized. This allows directory traversal, in which the file is saved outside of the intended storage location. If anonymous content creation is enabled, this allows an unauthenticated attacker to upload an executable file, such as a .jsp file, that can lead to remote code execution.
The weakness was published 07/18/2022 as 167365. It is possible to read the advisory at packetstormsecurity.com. The identification of this vulnerability is CVE-2022-26352 since 03/02/2022. Technical details as well as a exploit are known. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
It is declared as attacked. The CISA Known Exploited Vulnerabilities Catalog lists this issue since 08/25/2022 with a due date of 09/15/2022:
Apply updates per vendor instructions.There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.0VulDB Meta Temp Score: 9.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 9.8
CNA Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Pathname traversalCWE: CWE-21 / CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Attacked
EPSS Score: 🔍
EPSS Percentile: 🔍
KEV Added: 🔍
KEV Due: 🔍
KEV Remediation: 🔍
KEV Ransomware: 🔍
KEV Notice: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/02/2022 🔍07/18/2022 🔍
07/18/2022 🔍
02/03/2025 🔍
Sources
Advisory: 167365Status: Confirmed
CVE: CVE-2022-26352 (🔍)
GCVE (CVE): GCVE-0-2022-26352
GCVE (VulDB): GCVE-100-204035
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/18/2022 07:25Updated: 02/03/2025 20:58
Changes: 07/18/2022 07:25 (40), 08/01/2022 13:03 (18), 04/27/2024 15:09 (27), 09/25/2024 00:04 (3), 02/03/2025 20:58 (14)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.