VDB-162101 · CVE-2020-15488 · GCVE-0-2020-15488

Re:Desk 2.3 File Upload privileges management

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.
6.4	$0-$5k	0.00

Summaryinfo

A vulnerability identified as critical has been detected in Re:Desk 2.3. Impacted is an unknown function of the component File Upload. The manipulation leads to privileges management. This vulnerability is documented as CVE-2020-15488. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Re:Desk 2.3. This issue affects some unknown functionality of the component File Upload. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Re:Desk 2.3 allows insecure file upload.

The weakness was released 09/30/2020. The identification of this vulnerability is CVE-2020-15488 since 07/01/2020. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

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

Entries connected to this vulnerability are available at VDB-162104 and VDB-162100. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Re:Desk

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.4
VulDB Meta Temp Score: 6.4

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

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Privileges management
CWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
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 Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

07/01/2020 🔍
09/30/2020 +91 days 🔍
10/01/2020 +1 days 🔍
11/15/2020 +45 days 🔍

Sourcesinfo

Status: Not defined

CVE: CVE-2020-15488 (🔍)
GCVE (CVE): GCVE-0-2020-15488
GCVE (VulDB): GCVE-100-162101
See also: 🔍

Entryinfo

Created: 10/01/2020 09:34
Updated: 11/15/2020 07:04
Changes: 10/01/2020 09:34 (34), 10/01/2020 09:39 (3), 11/14/2020 09:32 (5), 11/15/2020 07:04 (14)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.