CVE-2013-3900: WinVerifyTrust Signature Validation Vulnerability
Microsoft · Windows 10 Version 1809
Vendor fix available · Affected: Microsoft Windows 10 Version 1809 · Exploitation: in CISA KEV since 10 Jan 2022
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
ExploitationIn CISA KEV
- In CISA KEVCISA KEV catalogue10 Jan 2022
- Exploited (reported): not seen
- Scanning observed: not seen
- Proof of concept public: not seen
- Not established: not seen
Higher than 98% of scored CVEs
DescriptionCVE.org
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.
Affected products20
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Microsoft · Windows 10 Version 1809Versions not stated
- Microsoft · Windows 10 Version 1809Versions not stated
- Microsoft · Windows Server 2019Versions not stated
- Microsoft · Windows Server 2019 (Server Core installation)Versions not stated
- Microsoft · Windows Server 2022Versions not stated
- Microsoft · Windows 11 version 21H2Versions not stated
- Microsoft · Windows 10 Version 21H2Versions not stated
- Microsoft · Windows 11 version 22H2Versions not stated
- Microsoft · Windows 10 Version 22H2Versions not stated
- Microsoft · Windows Server 2025 (Server Core installation)Versions not stated
- Microsoft · Windows 11 version 22H3Versions not stated
- Microsoft · Windows 11 Version 23H2Versions not stated
- Microsoft · Windows Server 2022, 23H2 Edition (Server Core installation)Versions not stated
- Microsoft · Windows 11 Version 24H2Versions not stated
- Microsoft · Windows Server 2025Versions not stated
- Microsoft · Windows 10 Version 1507Versions not stated
- Microsoft · Windows 10 Version 1607Versions not stated
- Microsoft · Windows Server 2016Versions not stated
- Microsoft · Windows Server 2016 (Server Core installation)Versions not stated
- Microsoft · Windows Server 2008 Service Pack 2Versions not stated
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Exploited in the wild. Listed in the CISA Known Exploited Vulnerabilities catalogue.
- CISA KEV
- Listed since 10 Jan 2022 · catalogue entry
- Public check
- No public nuclei template
- Vendor
- Microsoft
- Published
- December 2013
What changed
- CISA added it to the KEV catalogue CISA
CoverageNo articles yet
No CyberSIXT article names CVE-2013-3900 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.