Microsoft Exchange Server 2013 CU23/2016 CU20/2019 CU9 privilege escalation

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.
7.7$0-$5k0.00

Summaryinfo

A vulnerability was found in Microsoft Exchange Server 2013 CU23/2016 CU20/2019 CU9. It has been rated as critical. This affects an unknown function. Performing a manipulation results in an unknown weakness. This vulnerability is identified as CVE-2021-28482. The attack can be initiated remotely. Additionally, an exploit exists. To fix this issue, it is recommended to deploy a patch.

Detailsinfo

A vulnerability was found in Microsoft Exchange Server 2013 CU23/2016 CU20/2019 CU9 (Groupware Software). It has been classified as critical. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was released 04/13/2021 as confirmed security guidance (Website). It is possible to read the advisory at portal.msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2021-28482. Technical details are unknown but a public exploit is available.

A public exploit has been developed by Shadow0ps in Python and been published 3 weeks after the advisory. The exploit is shared for download at github.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.1

VulDB Base Score: 8.8
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 8.8
Vendor Vector (Microsoft): 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Shadow0ps
Programming Language: 🔍
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Exploit Delay Time: 🔍

Timelineinfo

03/15/2021 🔍
04/13/2021 +29 days 🔍
04/13/2021 +0 days 🔍
04/13/2021 +0 days 🔍
05/03/2021 +19 days 🔍
05/12/2021 +9 days 🔍

Sourcesinfo

Vendor: microsoft.com

Advisory: portal.msrc.microsoft.com
Status: Confirmed

CVE: CVE-2021-28482 (🔍)
GCVE (CVE): GCVE-0-2021-28482
GCVE (VulDB): GCVE-100-172851
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 04/13/2021 21:43
Updated: 05/12/2021 13:48
Changes: 04/13/2021 21:43 (13), 04/13/2021 21:44 (21), 04/13/2021 21:47 (19), 04/16/2021 15:54 (2), 04/16/2021 15:57 (16), 05/12/2021 13:48 (8)
Complete: 🔍
Committer: misc
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!