| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Cockpit up to 0.6.0. This affects an unknown function in the library lib/MongoLite/Database.php of the component JSON Data Handler. Performing a manipulation results in injection. This vulnerability is known as CVE-2020-35131. Remote exploitation of the attack is possible. Furthermore, an exploit is available. You should upgrade the affected component.
Details
A vulnerability was found in Cockpit up to 0.6.0. It has been classified as critical. This affects some unknown functionality in the library lib/MongoLite/Database.php of the component JSON Data Handler. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 01/09/2021 as 49390. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2020-35131. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1055 for this issue.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:lib/MongoLite/Database.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 0.6.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at Exploit-DB (49390). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: InjectionCWE: CWE-74 / CWE-707 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Cockpit 0.6.1
Patch: github.com
Timeline
12/11/2020 🔍01/09/2021 🔍
01/09/2021 🔍
02/10/2021 🔍
Sources
Advisory: 49390Status: Confirmed
CVE: CVE-2020-35131 (🔍)
GCVE (CVE): GCVE-0-2020-35131
GCVE (VulDB): GCVE-100-167505
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/09/2021 13:44Updated: 02/10/2021 18:58
Changes: 01/09/2021 13:44 (45), 02/10/2021 18:52 (3), 02/10/2021 18:58 (18)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.