POSCMS 3.2.10 Setting.php index $cache['setting']['ucssocfg'] code injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.9 | $0-$5k | 0.04 |
A vulnerability, which was classified as critical, has been found in POSCMS 3.2.10. Affected by this issue is the function index
of the file diy\module\member\controllers\admin\Setting.php. The manipulation of the argument $cache['setting']['ucssocfg']
with an unknown input leads to a code injection vulnerability. Using CWE to declare the problem leads to CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Impacted is confidentiality, integrity, and availability. CVE summarizes:
POSCMS 3.2.10 allows remote attackers to execute arbitrary PHP code via the diy\module\member\controllers\admin\Setting.php 'index' function because an attacker can control the value of $cache['setting']['ucssocfg'] in diy\module\member\models\Member_model.php and write this code into the api/ucsso/config.php file.
The bug was discovered 04/19/2018. The weakness was disclosed 04/19/2018 (Website). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2018-10235 since 04/19/2018. The exploitation is known to be easy. The attack may be launched remotely. The requirement for exploitation is a simple authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.
By approaching the search of inurl:diy\module\member\controllers\admin\Setting.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entry 116913 is pretty similar.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.7
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
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: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: no mitigation knownStatus: 🔍
Timeline
04/19/2018 🔍04/19/2018 🔍
04/19/2018 🔍
04/19/2018 🔍
04/21/2018 🔍
01/30/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-10235 (🔍)
See also: 🔍
Entry
Created: 04/21/2018 16:12Updated: 01/30/2020 10:17
Changes: 04/21/2018 16:12 (57), 01/30/2020 10:17 (1)
Complete: 🔍
Cache ID: 18:361:103
No comments yet. Languages: en.
Please log in to comment.