CMS Made Simple up to 2.2.6 $_COOKIE[$this->_loginkey] cryptographic issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in CMS Made Simple up to 2.2.6. This issue affects some unknown processing. Such manipulation of the argument $_COOKIE[$this->_loginkey] with the input 1 as part of Cookie leads to cryptographic issue.
This vulnerability is documented as CVE-2018-10084. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in CMS Made Simple up to 2.2.6 (Content Management System) and classified as critical. Affected by this issue is an unknown function. The manipulation of the argument $_COOKIE[$this->_loginkey] with the input value 1 leads to a cryptographic issue vulnerability. Using CWE to declare the problem leads to CWE-310. Impacted is confidentiality, integrity, and availability. CVE summarizes:
CMS Made Simple (CMSMS) through 2.2.6 contains a privilege escalation vulnerability from ordinary user to admin user by arranging for the eff_uid value within $_COOKIE[$this->_loginkey] to equal 1, because an SHA-1 cryptographic protection mechanism can be bypassed.
The bug was discovered 04/13/2018. The weakness was released 04/13/2018 (Website). The advisory is available at github.com. This vulnerability is handled as CVE-2018-10084 since 04/13/2018. The exploitation is known to be easy. The attack may be launched remotely. The successful exploitation requires a simple authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1600 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Entries connected to this vulnerability are available at VDB-116187, VDB-116183, VDB-116184 and VDB-116185. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
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: Cryptographic issueCWE: CWE-310
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: no mitigation knownStatus: 🔍
Timeline
04/13/2018 🔍04/13/2018 🔍
04/13/2018 🔍
04/13/2018 🔍
04/16/2018 🔍
01/24/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-10084 (🔍)
GCVE (CVE): GCVE-0-2018-10084
GCVE (VulDB): GCVE-100-116186
See also: 🔍
Entry
Created: 04/16/2018 09:15Updated: 01/24/2020 23:22
Changes: 04/16/2018 09:15 (58), 01/24/2020 23:22 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.