Microsoft · WinVerifyTrust function
CVE-2013-3900
WinVerifyTrust Signature Validation Vulnerability
Nedir
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
CISA: A remote code execution vulnerability exists in the way that the WinVerifyTrust function handles Windows Authenticode signature verification for PE files.
Ne yapmalı
Apply updates per vendor instructions.
ABD federal kurumları için son tarih: 10 Temmuz 2022
Microsoft için istismar edilen diğer açıklar
| Eklenme | Açık | Ürün | Önem | Saldırı olasılığı |
|---|---|---|---|---|
| 13 Eki 2026 | Command Injection | Windows | Yüksek 8,8 | 9,8% |
| 25 Eyl 2026 | Code Injection | SharePoint | Yüksek 8,8 | 8,2% |
| 8 Eyl 2026 | Link Following | Windows | Yüksek 7,8 | 0,4% |
| 8 Eyl 2026 | Heap-Based Buffer Overflow | Windows | Yüksek 7,8 | 0,4% |
| 26 Ağu 2026 | Remote Code Execution | SQL Server | Yüksek 8,8 | 57% |
| 18 Ağu 2026 | Double Free | Internet Key Exchange (IKE) Service Extensions | Kritik 9,8 | 77% |
| 18 Ağu 2026 | Weak Authentication | SharePoint | Kritik 9,1 | 70% |
| 11 Ağu 2026 | Windows Ancillary Function Driver for WinSock Use-After-Free | Windows Ancillary Function Driver for WinSock | Yüksek 7,0 | 0,3% |
Kaynaklar: Known Exploited Vulnerabilities (CISA, kamu malı), CVE records (cve.org) ve EPSS (FIRST). Saldırı olasılığı, birinin önümüzdeki 30 günde açığı istismar etmeye çalışacağına dair EPSS tahminidir.