Actively exploited in the wild
Microsoft WinVerifyTrust function Remote Code Execution
Microsoft - WinVerifyTrust function · Listed in the CISA KEV since 2022-01-10. This indicates confirmed attacks in production environments.
Required action: Apply updates per vendor instructions.
CVE-2013-3900
MediumCVSS 5.5KEVSummary
A remote code execution vulnerability exists in the way the WinVerifyTrust function handles Windows Authenticode signature verification for portable executable (PE) files. An attacker could modify an existing signed executable to add malicious code without invalidating the signature. Microsoft does not plan to enforce stricter verification by default — it requires manually setting the EnableCertPaddingCheck registry key.
Risk Assessment
Successful exploitation allows an attacker to take complete control of the affected system, including installing programs, viewing, changing, or deleting data, and creating accounts with full user rights. The risk is especially high for users with administrative privileges.
Recommendation
Set the EnableCertPaddingCheck registry key on all supported versions of Windows 10 and Windows 11 to enable stricter Authenticode signature verification. No security update is required — only the registry key configuration is needed.
Other vulnerabilities in Microsoft Windows
See all- CVE-2017-8467High
In Microsoft Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016, there is a vulnerability that allows elevation of privilege due to the way it handles objects in memory.
- CVE-2016-0009High
The vulnerability in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, and Windows 10 Gold and 1511 allows remote attackers to execute arbitrary code via unspecified vectors.
- CVE-2024-21412HighActively exploited
Security feature bypass vulnerability in Internet Shortcut Files. Allows an attacker to bypass system security features.
- CVE-2023-21823HighActively exploited
Windows Graphics Component Remote Code Execution Vulnerability. Details are not provided in the description, but it allows remote code execution.
- CVE-2021-41379MediumActively exploited
Windows Installer Elevation of Privilege Vulnerability. Details are not provided in the description, but it allows privilege escalation.
- CVE-2020-1054HighActively exploited
An elevation of privilege vulnerability exists in Windows when the Windows kernel-mode driver fails to properly handle objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode, install programs, view/change/delete data, or create new accounts with full user rights.
- CVE-2013-7331MediumActively exploited
The Microsoft.XMLDOM ActiveX control in Microsoft Windows 8.1 and earlier allows remote attackers to determine the existence of local pathnames, UNC share pathnames, intranet hostnames, and intranet IP addresses by examining error codes, as demonstrated by a res:// URL, and exploited in the wild in February 2014.
- CVE-2000-0168Medium
Microsoft Windows 9x operating systems allow an attacker to cause a denial of service via a pathname that includes file device names, aka the 'DOS Device in Path Name' vulnerability.
- CVE-2026-50476High
Use-After-Free vulnerability in Microsoft Windows allows an authorized attacker to elevate privileges locally.
- CVE-2024-30072High
A remote code execution vulnerability exists in Microsoft Event Trace Log file parsing. An attacker can exploit a specially crafted ETW file to take control of the affected system.
Original NVD description (English source)
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 could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of this vulnerability requires that a user or application run or install a specially crafted, signed PE file. An attacker could modify an... See more at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900