Vulnerabilities (CVE)

Windows Error Reporting Service Elevation of Privilege Vulnerability

.NET Framework Information Disclosure Vulnerability

SmartScreen Prompt Security Feature Bypass Vulnerability

Windows MSHTML Platform Security Feature Bypass Vulnerability

Windows DWM Core Library Elevation of Privilege Vulnerability

Windows Kernel Elevation of Privilege Vulnerability

Windows Kernel-Mode Driver Elevation of Privilege Vulnerability

Windows Installer Elevation of Privilege Vulnerability

Windows Hyper-V Elevation of Privilege Vulnerability

Windows Kernel Elevation of Privilege Vulnerability

Windows Power Dependency Coordinator Elevation of Privilege Vulnerability

Windows MSHTML Platform Spoofing Vulnerability

Scripting Engine Memory Corruption Vulnerability

Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability

Windows Mark of the Web Security Feature Bypass Vulnerability

Windows Mark of the Web Security Feature Bypass Vulnerability

Windows MSHTML Platform Spoofing Vulnerability

Windows DWM Core Library Elevation of Privilege Vulnerability

Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability

Microsoft WordPad Information Disclosure Vulnerability

Windows Mark of the Web Security Feature Bypass Vulnerability

Microsoft Streaming Service Proxy Elevation of Privilege Vulnerability

Windows Error Reporting Service Elevation of Privilege Vulnerability

Windows Search Remote Code Execution Vulnerability

Windows CNG Key Isolation Service Elevation of Privilege Vulnerability

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Microsoft Streaming Service Elevation of Privilege Vulnerability

Windows MSHTML Platform Elevation of Privilege Vulnerability

Windows SmartScreen Security Feature Bypass Vulnerability

Windows SmartScreen Security Feature Bypass Vulnerability

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Windows SmartScreen Security Feature Bypass Vulnerability

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 origi ... 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

Show More

Windows Wi-Fi Driver Remote Code Execution Vulnerability

Windows Themes Spoofing Vulnerability

Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability

Windows Themes Spoofing Vulnerability

Windows Remote Access Connection Manager Information Disclosure Vulnerability

Windows Common Log File System Driver Elevation of Privilege Vulnerability

Windows Cryptographic Services Remote Code Execution Vulnerability