FineCMS 5.2.0 Membr API v5/config/system.php SYS_KEY key management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in FineCMS 5.2.0. It has been rated as critical. Affected by this issue is some unknown functionality of the file v5/config/system.php of the component Membr API. The manipulation of the argument SYS_KEY as part of PHP File leads to key management. This vulnerability is documented as CVE-2017-16920. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in FineCMS 5.2.0. It has been rated as critical. This issue affects an unknown function of the file v5/config/system.php of the component Membr API. The manipulation of the argument SYS_KEY as part of a PHP File leads to a key management vulnerability. Using CWE to declare the problem leads to CWE-320. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
v5/config/system.php in dayrui FineCms 5.2.0 has a default SYS_KEY value and does not require key regeneration for each installation, which allows remote attackers to upload arbitrary .php files via a member api swfupload action to index.php.
The bug was discovered 11/21/2017. The weakness was released 11/21/2017 (Website). The advisory is shared at gitee.com. The identification of this vulnerability is CVE-2017-16920 since 11/21/2017. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
By approaching the search of inurl:v5/config/system.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.
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: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: Key managementCWE: CWE-320
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: 🔍
Patch: gitee.com
Timeline
11/21/2017 🔍11/21/2017 🔍
11/21/2017 🔍
11/21/2017 🔍
11/22/2017 🔍
01/11/2023 🔍
Sources
Advisory: ff4b7ad3c3fbd3245b3bb7bc774d20c9705d9882Status: Not defined
CVE: CVE-2017-16920 (🔍)
GCVE (CVE): GCVE-0-2017-16920
GCVE (VulDB): GCVE-100-109781
Entry
Created: 11/22/2017 07:56Updated: 01/11/2023 08:56
Changes: 11/22/2017 07:56 (57), 12/09/2019 11:14 (1), 01/11/2023 08:56 (4)
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.