Cosmo 1.0.0Beta6 Database Prefix Field install.php code injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Cosmo 1.0.0Beta6. This affects an unknown part of the file install.php of the component Database Prefix Field Handler. The manipulation leads to code injection. This vulnerability is uniquely identified as CVE-2018-10429. It is possible to initiate the attack remotely. There is no exploit available. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Details
A vulnerability was found in Cosmo 1.0.0Beta6. It has been rated as critical. Affected by this issue is an unknown function of the file install.php of the component Database Prefix Field Handler. The manipulation 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:
Cosmo 1.0.0Beta6 allows attackers to execute arbitrary PHP code via the Database Prefix field on the Database Info screen of install.php.
The bug was discovered 04/26/2018. The weakness was disclosed 04/26/2018 (Website). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2018-10429 since 04/26/2018. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. 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:install.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 best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
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: 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/26/2018 🔍04/26/2018 🔍
04/26/2018 🔍
04/26/2018 🔍
04/27/2018 🔍
03/07/2023 🔍
Sources
Advisory: 405Status: Not defined
CVE: CVE-2018-10429 (🔍)
GCVE (CVE): GCVE-0-2018-10429
GCVE (VulDB): GCVE-100-117152
Entry
Created: 04/27/2018 08:44 AMUpdated: 03/07/2023 08:41 PM
Changes: 04/27/2018 08:44 AM (55), 01/31/2020 09:33 PM (1), 03/07/2023 08:41 PM (3)
Complete: 🔍
Cache ID: 18:982:40
No comments yet. Languages: en.
Please log in to comment.