CVE-2020-0638
Microsoft Update Notification Manager Privilege Escalation Vulnerability
Microsoft Update Notification Manager
An elevation of privilege vulnerability exists in the way the Update Notification Manager handles files.To exploit this vulnerability, an attacker would first have to gain execution on the victim system, aka 'Update Notification Manager Elevation of Privilege Vulnerability'.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 23 May 2022. US federal agencies were required to remediate it by 13 June 2022. CISA records this vulnerability as known to be used in ransomware campaigns.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 2.5%, which is higher than 85.2% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2020-0638 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2020-0638.
What does CVE-2020-0638 affect?
CVE-2020-0638 affects Microsoft Update Notification Manager. An elevation of privilege vulnerability exists in the way the Update Notification Manager handles files.To exploit this vulnerability, an attacker would first have to gain execution on the victim system, aka 'Update Notification Manager Elevation of Privilege Vulnerability'.
How severe is CVE-2020-0638?
CVE-2020-0638 is rated HIGH with a CVSS base score of 7.8. EPSS puts the probability of exploitation in the next 30 days at 2.5%, higher than 85.2% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 13 June 2022.
How should organisations respond to CVE-2020-0638?
Apply the vendor patch for Microsoft Update Notification Manager as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.