CVE-2013-3900

Description

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

Severity
MEDIUM
CVSS v3
5.5
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C · source cna
Exploit chance (EPSS)
44.647%
chance of exploitation in the next 30 days
higher than 98.8% of scored CVEs · 2026-11-17
CISA KEV
Listed
added 2022-01-10
Public exploit code
None public
Attackers are using this, but no public exploit code was found in these sources.
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA Known Exploited Vulnerabilities entry

Vulnerability nameMicrosoft WinVerifyTrust function Remote Code Execution
Vendor / productMicrosoft / WinVerifyTrust function
Date added2022-01-10
Federal remediation due date2022-07-10
Required actionApply updates per vendor instructions.
Known ransomware campaign useUnknown

CISA SSVC decision points

Exploitationactive
Automatableno
Technical impactpartial
Scored2025-02-10

Timeline

  1. 2013-12-11Published by the CNA00:00 UTC
  2. 2022-01-10Added to the CISA KEV catalog2952 days after publication
  3. 2025-02-10CISA SSVC decision recorded4079 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
microsoft windows_10_1507
microsoft windows_10_1607
microsoft windows_10_1809
microsoft windows_10_1909
microsoft windows_10_20h2
microsoft windows_10_21h1
microsoft windows_10_21h2
microsoft windows_10_22h2
microsoft windows_11_21h2
microsoft windows_11_22h2
microsoft windows_11_23h2
microsoft windows_11_24h2
microsoft windows_7
microsoft windows_8.1
microsoft windows_rt_8.1
microsoft windows_server_2008
microsoft windows_server_2008_r2
microsoft windows_server_2008_sp2
microsoft windows_server_2012
microsoft windows_server_2012_r2

26 vulnerable vendor/product pairs in total; the first 20 are shown. The cve_products API lists them page by page, with versions.

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources