CVE-2013-3900
Microsoft WinVerifyTrust function Remote Code Execution
Published Dec 10, 2013 · updated Oct 7, 2026 · microsoft windows 10 1507
Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update the Security Updates table and to inform customers that the EnableCertPaddingCheck is available in all currently supported versions of Windows 10 and Windows 11. While the format is different from the original CVE published in 2013, except for clarifications about how to configure the EnableCertPaddingCheck registry value, the information herein remains unchanged from the original text published on December 10, 2013, Microsoft does not plan to enforce the stricter verification behavior as a default functionality on supported releases of Microsoft Windows. This behavior remains available as an opt-in feature via reg key setting, and is available on supported editions of Windows released since December 10, 2013. This includes all currently supported versions of Windows 10 and Windows 11. The supporting code for this reg key was incorporated at the time of release for Windows 10 and Windows 11, so no security update is required; however, the reg key must be set. See the Security Updates table for the list of affected software. Vulnerability Description A remote code execution vulnerability exists in the way that the WinVerifyTrust function handles Windows Authenticode signature verification for portable executable (PE) files. An anonymous attacker could exploit the vulnerability by modifying an existing signed executable file to leverage unverified portions of the file in such a way as to add malicious code to the file without invalidating the signature. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. If a user is logged on with administrative user rights, an attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker c
Timeline
Detection, updates, and resolution for this record.
Dec 10, 2013 · Catalog
Detected
Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update the Security Updates table and to inform customers that the EnableCertPaddingCheck is available in all currently supported versions of Windows 10 and Windows 11. While the format is different from the original CVE published in 2013, except for clarifications about how to configur
Jan 10, 2022 · CISA KEV
Known exploited
Apply updates per vendor instructions.
Jul 10, 2022 · CISA KEV
Remediation due
Apply updates per vendor instructions.
Oct 7, 2026 · Catalog
Updated
Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update the Security Updates table and to inform customers that the EnableCertPaddingCheck is available in all currently supported versions of Windows 10 and Windows 11. While the format is different from the original CVE published in 2013, except for clarifications about how to configur
Required action
Apply updates per vendor instructions.
CISA due date Jul 10, 2022
Affected
- cpe microsoft/windows 10 1507version unspecified
- cpe microsoft/windows 10 1607version unspecified
- cpe microsoft/windows 10 1809version unspecified
- cpe microsoft/windows 10 1909version unspecified
- cpe microsoft/windows 10 20h2version unspecified
- vendor Microsoft WinVerifyTrust functionversion unspecified
Sources
- CISA KEVCVE-2013-3900
A remote code execution vulnerability exists in the way that the WinVerifyTrust function handles Windows Authenticode signature verification for PE files.
cisa.gov - CVE.orgCVE-2013-3900
Official CVE identifier
cve.org - FIRST EPSSCVE-2013-3900
30-day exploitation probability 44.6%
first.org - NIST NVDCVE-2013-3900
Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update the Security Updates table and to inform customers that the EnableCertPaddingCheck is available in all currently supported versions of Windows 10 and Windows 11
nvd.nist.gov