Skip to content
Server Security Center
KEVmedium5.5

CVE-2013-3900: Microsoft WinVerifyTrust function Remote Code Execution

Microsoft WinVerifyTrust function · listed in the CISA catalog of actively exploited vulnerabilities since 2022-01-10.

CVSS v3.1 (CVE record)
5.5
medium
EPSS (exploit probability, 30 days)
45%
higher than 98.8% of all CVEs
Added to CISA KEV
2022-01-10
US federal due date 2022-07-10
Automatable (CISA SSVC)
no
technical impact: partial

What is CVE-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.

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 msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 180932-bit, x64, ARM64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2019x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2022x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 11 version 21H2x64, ARM64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 22H2x64, ARM64, 32-bit
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 11 version 22H3ARM64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

Show 16 more products
  • Microsoft Windows 11 Version 23H2x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2025x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2016x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2012x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2012 R2x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
  • CISA's deadline for US federal agencies: 2022-07-10 (passed) – a useful benchmark for everyone else, too.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Partial – limited control or information

Weakness: CWE-347 Improper Verification of Cryptographic Signature

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.