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 https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
The record classifies CVE-2013-3900 under weakness class CWE-347. Its CVSS v3 base vector states that the flaw requires local access to the host, needs no prior authentication, needs a user to take an action first, and has high impact on integrity. 12 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 4726 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 5.5 — MEDIUM
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 - EPSS (FIRST)
- 44.6% probability of exploitation in the next 30 days, higher than 98.7% of all scored CVEs
- CISA KEV
- Listed since 2022-01-10, federal remediation deadline 2022-07-10
- Threadlinqs priority
- 9/10 — CISA KEV-listed, which Threadlinqs floors at 9
- Published
- 2013-12-11
Is CVE-2013-3900 being exploited?
CISA added CVE-2013-3900 to the Known Exploited Vulnerabilities catalog on 2022-01-10, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2022-07-10 under BOD 22-01. Weaponised exploit code for CVE-2013-3900 is publicly available. 11 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 48 in the Threadlinqs vulnerability feed.
- norvethil/CVE-2013-3900-PowerShell-PoC (github)
- CyberCondor/Fix-WinVerifyTrustSignatureValidationVuln (github)
- OtisSymbos/CVE-2013-3900-WinTrustVerify (github)
- pkblanks/Remediating-CVE-2013-3900-EnableCertPaddingCheck- (github)
- snoopopsec/vulnerability-CVE-2013-3900 (github)
- Securenetology/CVE-2013-3900 (github)
- AdenilsonSantos/WinVerifyTrust (github)
- DavidBr27/CVE-2013-3900-Remediation-Script (github)
Affected products and versions
- Microsoft: Windows 10 Version 1809, Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022, Windows 11 version 21H2, Windows 10 Version 21H2, Windows 11 version 22H2, Windows 10 Version 22H2, Windows Server 2025 (Server Core installation), Windows 11 version 22H3, Windows 11 Version 23H2, Windows Server 2022, 23H2 Edition (Server Core installation)
How to fix CVE-2013-3900
Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900. Because CVE-2013-3900 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2022-07-10. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2013-3900
1 tracked threat in the Threadlinqs corpus references CVE-2013-3900, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS, CISA KEV, GitHub Security Advisories, public proof-of-concept repositories.