Nextcloud Server 19.0.0 API Call credentials storage

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability was found in Nextcloud Server 19.0.0. It has been declared as problematic. This issue affects some unknown processing of the component API Call Handler. Executing a manipulation can lead to credentials storage. This vulnerability is tracked as CVE-2020-8183. No exploit exists.

Detailsinfo

A vulnerability was found in Nextcloud Server 19.0.0 (Cloud Software). It has been declared as problematic. This vulnerability affects some unknown processing of the component API Call Handler. The manipulation with an unknown input leads to a credentials storage vulnerability. The CWE definition for the vulnerability is CWE-256. Storing a password in plaintext may result in a system compromise. As an impact it is known to affect confidentiality.

The weakness was disclosed 11/03/2020. The advisory is shared for download at hackerone.com. This vulnerability was named CVE-2020-8183. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1552.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.5

VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Credentials storage
CWE: CWE-256 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/28/2020 🔍
11/03/2020 +280 days 🔍
11/03/2020 +0 days 🔍
12/01/2020 +28 days 🔍

Sourcesinfo

Advisory: hackerone.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2020-8183 (🔍)
GCVE (CVE): GCVE-0-2020-8183
GCVE (VulDB): GCVE-100-164212

Entryinfo

Created: 11/03/2020 09:22
Updated: 12/01/2020 14:30
Changes: 11/03/2020 09:22 (37), 12/01/2020 14:26 (2), 12/01/2020 14:30 (18)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!