Skip to content
English

Patch first › Microsoft

Exploited CVE from 2013, added in 2022

CVE-2013-3900

Microsoft Windows · Operating systems

Microsoft WinVerifyTrust function Remote Code Execution

At a glance

Exploited. Added to CISA’s catalog of exploited vulnerabilities on January 10, 2022.

Affected product: Microsoft Windows (category Operating systems, indicative classification). Name in CISA’s catalog: Microsoft WinVerifyTrust function.

Microsoft component: Cryptography and TLS (CryptoAPI, CNG, Schannel) (Windows: platform security).

What should I do?

Apply the security update from Microsoft.

Deadline set by CISA for US federal agencies: 181 days (due July 10, 2022). It only binds those agencies, but it is a useful measure of urgency.

Original text of the required action (CISA)

Apply updates per vendor instructions.

Timeline

  1. Vulnerability published Publication date (NVD)
  2. Exploitation confirmed Added to CISA’s KEV catalog
  3. CISA deadline Remediation deadline set for US federal agencies

The facts, with their sources

Exploitation confirmed
Yes, on January 10, 2022 Date added to the catalog of exploited vulnerabilities. Exploitation itself may have started earlier. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
Ransomware
No known use to date That does not guarantee it is not being used: the information is not public. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
Hunt for compromise
Not requested by CISA Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
CISA required action
Apply the security update from Microsoft. Rewritten by this site from CISA’s original text. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
CISA deadline
July 10, 2022, 181 days Set for US federal agencies: a measure of urgency, not an obligation elsewhere. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
Microsoft patch
Not available Source: Security Update Guide, collected September 29, 2026 at 14:57 UTC
Vulnerability published
December 11, 2013 Source: National Vulnerability Database (NVD), collected September 29, 2026 at 15:00 UTC
Product according to CISA
Microsoft WinVerifyTrust function Filed by this site under “Operating systems” (indicative classification). Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Technical detail of the score: attack vector, complexity, impact. Source: National Vulnerability Database (NVD), collected September 29, 2026 at 15:00 UTC

Severity and activity

8.8 / 10 CVSS severity: high

Score from the NVD. Collected Sep 29, 2026.

— Probability of exploitation in the next 30 days (EPSS)

FIRST’s EPSS model. Since exploitation is already confirmed, this figure is mostly useful to compare activity. Collected Sep 29, 2026.

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 [lien retiré]

Official description from the NVD, collected Sep 29, 2026. CVE® description © The MITRE Corporation.

A remote code execution vulnerability exists in the way that the WinVerifyTrust function handles Windows Authenticode signature verification for PE files.

Summary from CISA (KEV catalog).

CERT-FR advisories

No advisory among the latest CERT-FR publications this site follows. That does not mean there are none.

Information reused under the Open Licence 2.0 (Etalab); the date of last update is shown for each advisory. This site is neither affiliated with nor endorsed by ANSSI.

Sources for this page