Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY1 SECURITY RECORD

Microsoft

Netlogon

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2020-1472 17 Aug 2020 Windows Server version 2004: 10.0.0 < publication; Windows Server 2019: 10.0.0 < publication; Windows Server 2019 (Server Core installation): 10.0.0 < publication; Windows Server, version 1909 (Server Core installation): 10.0.0 < publication; Windows Server, version 1903 (Server Core installation): 10.0.0 < publication; Windows Server 2016: 10.0.0 < publication; Windows Server 2016 (Server Core installation): 10.0.0 < publication; Windows Server 2008 R2 Service Pack 1: 6.1.0 < publication; Windows Server 2008 R2 Service Pack 1 (Server Core installation): 6.0.0 < publication; Windows Server 2012: 6.2.0 < publication; Windows Server 2012 (Server Core installation): 6.2.0 < publication; Windows Server 2012 R2: 6.3.0 < publication; Windows Server 2012 R2 (Server Core installation): 6.3.0 < publication; Windows Server version 20H2: 10.0.0 < publication Version Windows 10 of the Microsoft Windows includes a fix for this vulnerability and is available for download here: • https://www.microsoft.com/en-in/software-download/windows10 • Reboot is required Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.