dotCMS up to 3.3.1 REST API api/content/save/1 stName sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in dotCMS up to 3.3.1. It has been rated as critical. Impacted is an unknown function of the file api/content/save/1 of the component REST API. Performing a manipulation of the argument stName results in sql injection. This vulnerability is known as CVE-2016-2355. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability was found in dotCMS up to 3.3.1 (Content Management System). It has been classified as critical. This affects an unknown function of the file api/content/save/1 of the component REST API. The manipulation of the argument stName with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SQL injection vulnerability in the REST API in dotCMS before 3.3.2 allows remote attackers to execute arbitrary SQL commands via the stName parameter to api/content/save/1.
The bug was discovered 12/20/2016. The weakness was published 12/19/2016 with Tencent (Website). The advisory is shared at dotcms.com. This vulnerability is uniquely identified as CVE-2016-2355 since 02/12/2016. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
Upgrading to version 3.3.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 94992†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD 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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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 |
OpenVAS ID: 103306
OpenVAS Name: dotCMS Multiple Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: dotCMS 3.3.2
Timeline
02/12/2016 🔍04/12/2016 🔍
12/19/2016 🔍
12/19/2016 🔍
12/20/2016 🔍
12/20/2016 🔍
10/12/2022 🔍
Sources
Advisory: 8848Organization: Tencent
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-2355 (🔍)
GCVE (CVE): GCVE-0-2016-2355
GCVE (VulDB): GCVE-100-94605
SecurityFocus: 94992 - dotCMS 'stName' Parameter SQL Injection Vulnerability
Entry
Created: 12/20/2016 07:57Updated: 10/12/2022 11:05
Changes: 12/20/2016 07:57 (63), 07/11/2019 16:12 (7), 10/12/2022 11:05 (3)
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.