Microsoft Windows up to Server 2019 Error Reporting information disclosure
|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 has been found in Microsoft Windows (Operating System) and classified as problematic. Affected by this vulnerability is an unknown code of the component Error Reporting. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. As an impact it is known to affect confidentiality.
The weakness was published 07/14/2020 as confirmed security update guide (Website). The advisory is shared at portal.msrc.microsoft.com. The public release has been coordinated with Microsoft. This vulnerability is known as CVE-2020-1420 since 11/04/2019. The attack can be launched remotely. A single authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 10/30/2020). The advisory points out:
An information disclosure vulnerability exists when Windows Error Reporting improperly handles file operations.
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.1
VulDB Meta Temp Score: 4.9
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 5.5
Vendor Vector (Microsoft): 🔒
NVD Base Score: 5.5
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: Information disclosure (CWE-200)
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceThreat: 🔍
Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒
Timeline11/04/2019 CVE assigned
07/14/2020 +253 days Advisory disclosed
07/14/2020 +0 days Countermeasure disclosed
07/15/2020 +1 days VulDB entry created
10/30/2020 +107 days VulDB last update
CVE: CVE-2020-1420 (🔒)
scip Labs: https://www.scip.ch/en/?labs.20161215
See also: 🔒
EntryCreated: 07/15/2020 10:25 AM
Updated: 10/30/2020 08:18 AM
Changes: (1) source_cve_assigned
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!