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…
Browse: All 2013 CVEs · All vendors
- CVSS score
- 5.5 Medium
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N- CISA KEV
- Yes — actively exploited (added 2022-01-10, remediation due 2022-07-10)
- Weakness (CWE)
- CWE-347
- Published
- 2013-12-11
- Last modified
- 2026-06-16
- NVD status
- Analyzed
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
Affected products
- 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
Affected ranges per NVD CPE data; confirm exact versions in the vendor advisory.
Required action (CISA)
Apply updates per vendor instructions. Federal remediation deadline: 2022-07-10.
How to prioritize this
This vulnerability is on the CISA KEV list, meaning it is being actively exploited — treat it as urgent regardless of the raw CVSS number. Use the live CVE lookup for the latest NVD data, and the CVSS 3.1 calculator to model your own environmental score. For the actively exploited vulnerabilities that matter this week, read The Exploit HQ daily security brief.
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
- http://blogs.technet.com/b/srd/archive/2013/12/10/ms13-098-update-to-enhance-the-security-of-authenticode.aspx
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2013/ms13-098
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2013-3900
FAQ
Is CVE-2013-3900 actively exploited?
Yes. CISA added CVE-2013-3900 to its Known Exploited Vulnerabilities (KEV) catalog on 2022-01-10, with a federal remediation deadline of 2022-07-10. A KEV listing means real-world exploitation is confirmed, so patching this should be prioritized above many higher-CVSS bugs that aren't being exploited.
What is the CVSS score of CVE-2013-3900?
CVE-2013-3900 has a CVSS base score of 5.5 (Medium). Its vector string is CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N.
Related vulnerabilities
- CVE-2026-96951 — Microsoft Windows
- CVE-2026-65660 — Microsoft SharePoint
- CVE-2026-81963 — Microsoft Windows
- CVE-2026-85880 — Microsoft Windows
- CVE-2019-1068 — Microsoft SQL Server
- CVE-2026-33824 — Microsoft Internet Key Exchange (IKE) Serv
Data source: NVD & CISA KEV. Shown as-is; nothing added. Last generated from NVD data — re-check the live tool for updates.
kev brief
Patch what's actually being exploited.
Subscribe and get the KEV Patch Priority Playbook, free, in your inbox now.
Free. No spam. Unsubscribe anytime. Delivered by Beehiiv.