Microsoft SharePoint 2010 SP2/2013 SP1/2016/2019 Update denial of service
|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.
A vulnerability was found in Microsoft SharePoint 2010 SP2/2013 SP1/2016/2019 (Groupware Software). It has been classified as problematic. This affects an unknown code of the component Update Handler. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. This is going to have an impact on availability. The summary by CVE is:
Microsoft SharePoint Denial of Service Update
The weakness was shared 04/13/2021 as confirmed security guidance (Website). The advisory is shared at portal.msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2021-28450 since 03/15/2021. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/16/2021). MITRE ATT&CK project uses the attack technique T1499 for this issue.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
CVSSv3VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.4
VulDB Base Score: 5.0
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 5.0
Vendor Vector (Microsoft): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Denial of service
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceThreat: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline03/15/2021 CVE assigned
04/13/2021 +29 days VulDB entry created
04/13/2021 +0 days Advisory disclosed
04/13/2021 +0 days Countermeasure disclosed
04/16/2021 +3 days VulDB last update
CVE: CVE-2021-28450 (🔒)
EntryCreated: 04/13/2021 10:03 PM
Updated: 04/16/2021 05:24 PM
Changes: (2) source_cve_assigned source_cve_nvd_summary
Might our Artificial Intelligence support you?
Check our Alexa App!