| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Nextcloud Contacts 3.2.0. It has been classified as critical. This affects an unknown part. The manipulation leads to logic error. This vulnerability is documented as CVE-2020-8181. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Nextcloud Contacts 3.2.0 (Cloud Software). It has been rated as critical. This issue affects an unknown code block. The manipulation with an unknown input leads to a logic error vulnerability. Using CWE to declare the problem leads to CWE-840. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A missing file type check in Nextcloud Contacts 3.2.0 allowed a malicious user to upload any file as avatars.
The weakness was released 07/10/2020 (Website). The advisory is shared at hackerone.com. The identification of this vulnerability is CVE-2020-8181 since 01/28/2020. The exploitation is known to be easy. The attack may be initiated remotely. The requirement for exploitation is a simple authentication. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
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: Logic errorCWE: CWE-840
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: 🔍
0-Day Time: 🔍
Timeline
01/28/2020 🔍07/10/2020 🔍
07/11/2020 🔍
07/11/2020 🔍
Sources
Advisory: hackerone.comStatus: Not defined
CVE: CVE-2020-8181 (🔍)
GCVE (CVE): GCVE-0-2020-8181
GCVE (VulDB): GCVE-100-157841
Entry
Created: 07/11/2020 08:02Updated: 07/11/2020 08:07
Changes: 07/11/2020 08:02 (36), 07/11/2020 08:07 (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.