CVE Vulnerabilities

CVE-2020-1472

Use of Insufficiently Random Values

Published: Aug 17, 2020 | Modified: May 23, 2024
CVSS 3.x
10
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS 2.x
9.3 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C
RedHat/V2
RedHat/V3
9.8 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

An elevation of privilege vulnerability exists when an attacker establishes a vulnerable Netlogon secure channel connection to a domain controller, using the Netlogon Remote Protocol (MS-NRPC). An attacker who successfully exploited the vulnerability could run a specially crafted application on a device on the network. To exploit the vulnerability, an unauthenticated attacker would be required to use MS-NRPC to connect to a domain controller to obtain domain administrator access. Microsoft is addressing the vulnerability in a phased two-part rollout. These updates address the vulnerability by modifying how Netlogon handles the usage of Netlogon secure channels. For guidelines on how to manage the changes required for this vulnerability and more information on the phased rollout, see How to manage the changes in Netlogon secure channel connections associated with CVE-2020-1472 (updated September 28, 2020). When the second phase of Windows updates become available in Q1 2021, customers will be notified via a revision to this security vulnerability. If you wish to be notified when these updates are released, we recommend that you register for the security notifications mailer to be alerted of content changes to this advisory. See Microsoft Technical Security Notifications.

Weakness

The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.

Affected Software

Name Vendor Start Version End Version
Windows_server_1903 Microsoft * *
Windows_server_1909 Microsoft * *
Windows_server_2004 Microsoft - (including) - (including)
Windows_server_2008 Microsoft r2-sp1 (including) r2-sp1 (including)
Windows_server_2012 Microsoft - (including) - (including)
Windows_server_2012 Microsoft r2 (including) r2 (including)
Windows_server_2016 Microsoft - (including) - (including)
Windows_server_2019 Microsoft - (including) - (including)
Windows_server_20h2 Microsoft - (including) - (including)
Samba Ubuntu bionic *
Samba Ubuntu precise/esm *
Samba Ubuntu trusty *
Samba Ubuntu trusty/esm *
Samba Ubuntu xenial *
Red Hat Enterprise Linux 7 RedHat samba-0:4.10.16-9.el7_9 *
Red Hat Enterprise Linux 8 RedHat openchange-0:2.3-27.el8 *
Red Hat Enterprise Linux 8 RedHat samba-0:4.13.3-3.el8 *
Red Hat Enterprise Linux 8 RedHat openchange-0:2.3-27.el8 *
Red Hat Enterprise Linux 8 RedHat samba-0:4.13.3-3.el8 *
Red Hat Gluster Storage 3.5 for RHEL 7 RedHat samba-0:4.11.6-112.el7rhgs *
Red Hat Gluster Storage 3.5 for RHEL 8 RedHat samba-0:4.13.7-101.el8rhgs *

Potential Mitigations

  • Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds.
  • In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts.
  • Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a “random enough” number.

References