UCMS 1.4.6 Level HAndler user/editpost.php access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in UCMS 1.4.6. The affected element is an unknown function of the file user/editpost.php of the component Level HAndler. Performing a manipulation results in access control. This vulnerability was named CVE-2018-17037. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in UCMS 1.4.6. It has been classified as critical. This affects some unknown processing of the file user/editpost.php of the component Level HAndler. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
user/editpost.php in UCMS 1.4.6 mishandles levels, which allows escalation from the normal user level of 1 to the superuser level of 3.
The bug was discovered 09/12/2018. The weakness was presented 09/14/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-17037 since 09/13/2018. It is possible to initiate the attack remotely. Required for exploitation is a authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:user/editpost.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.
See VDB-124052, VDB-124051 and VDB-124050 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
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: 🔍
0-Day Time: 🔍
Timeline
09/12/2018 🔍09/13/2018 🔍
09/14/2018 🔍
09/14/2018 🔍
09/15/2018 🔍
03/23/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-17037 (🔍)
GCVE (CVE): GCVE-0-2018-17037
GCVE (VulDB): GCVE-100-124053
See also: 🔍
Entry
Created: 09/15/2018 07:55Updated: 03/23/2020 20:46
Changes: 09/15/2018 07:55 (57), 03/23/2020 20:46 (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.