Microsoft
WinVerifyTrust function
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2013-3900 | 11 Dec 2013 | Windows 10 Version 1809: N/A; Windows Server 2019: N/A; Windows Server 2019 (Server Core installation): N/A; Windows Server 2022: N/A; Windows 11 version 21H2: N/A; Windows 10 Version 21H2: N/A; Windows 11 version 22H2: N/A; Windows 10 Version 22H2: N/A; Windows Server 2025 (Server Core installation): N/A; Windows 11 version 22H3: N/A; Windows 11 Version 23H2: N/A; Windows Server 2022, 23H2 Edition (Server Core installation): N/A; Windows 11 Version 24H2: N/A; Windows Server 2025: N/A; Windows 10 Version 1507: N/A; Windows 10 Version 1607: N/A; Windows Server 2016: N/A; Windows Server 2016 (Server Core installation): N/A; Windows Server 2008 Service Pack 2: N/A; Windows Server 2008 Service Pack 2 (Server Core installation): N/A; Windows Server 2008 Service Pack 2: N/A; Windows Server 2008 R2 Service Pack 1: N/A; Windows Server 2008 R2 Service Pack 1 (Server Core installation): N/A; Windows Server 2012: N/A; Windows Server 2012 (Server Core installation): N/A; Windows Server 2012 R2: N/A; Windows Server 2012 R2 (Server Core installation): N/A | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | 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.