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, 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 existing signed file to include malicious code without invalidating the signature. This code would... See more at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
Metrics
Affected Vendors & Products
References
History
Fri, 22 Nov 2024 12:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Fri, 15 Nov 2024 15:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Microsoft windows 10 20h2
Microsoft windows 10 21h1 Microsoft windows 10 21h2 Microsoft windows 11 21h2 |
|
Weaknesses | CWE-20 | CWE-347 |
CPEs | cpe:2.3:o:microsoft:windows_10:1607:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_10:1809:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_10:1909:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_10:20h2:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_10:21h1:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_10:21h2:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_11:-:*:*:*:*:*:arm64:* cpe:2.3:o:microsoft:windows_11:-:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_server_2003:-:sp2:*:*:*:*:itanium:* cpe:2.3:o:microsoft:windows_server_2003:-:sp2:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_vista:-:sp2:*:*:-:*:x64:* cpe:2.3:o:microsoft:windows_xp:-:sp2:*:*:professional:*:x64:* cpe:2.3:o:microsoft:windows_xp:-:sp3:*:*:*:*:*:* |
cpe:2.3:o:microsoft:windows_10_1507:-:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_10_1607:-:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_10_1607:-:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_10_1809:-:*:*:*:*:*:arm64:* cpe:2.3:o:microsoft:windows_10_1809:-:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_10_1809:-:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_10_1909:-:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_10_20h2:-:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_10_21h1:-:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_10_21h2:-:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_11_21h2:-:*:*:*:*:*:arm64:* cpe:2.3:o:microsoft:windows_11_21h2:-:*:*:*:*:*:x64:* |
Vendors & Products |
Microsoft windows 10
Microsoft windows 11 Microsoft windows Server 2003 Microsoft windows Vista Microsoft windows Xp |
Microsoft windows 10 20h2
Microsoft windows 10 21h1 Microsoft windows 10 21h2 Microsoft windows 11 21h2 |
Thu, 14 Nov 2024 21:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Thu, 14 Nov 2024 20:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | The WinVerifyTrust function in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 does not properly validate PE file digests during Authenticode signature verification, which allows remote attackers to execute arbitrary code via a crafted PE file, aka "WinVerifyTrust Signature Validation 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, 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 existing signed file to include malicious code without invalidating the signature. This code would... See more at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900 |
Title | WinVerifyTrust Signature Validation Vulnerability | |
First Time appeared |
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 11 21h2 Microsoft windows Server 2008 R2 Microsoft windows Server 2008 Sp2 Microsoft windows Server 2012 R2 |
|
CPEs | cpe:2.3:o:microsoft:windows_10_1507:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_10_1507:*:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:arm64:* cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_10_1809:*:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_10_1909:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_10_1909:*:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_10_20H2:*:*:*:*:*:*:arm64:* cpe:2.3:o:microsoft:windows_10_20H2:*:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_10_21H1:*:*:*:*:*:*:arm64:* cpe:2.3:o:microsoft:windows_10_21H1:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_10_21H1:*:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_10_21H2:*:*:*:*:*:*:arm64:* cpe:2.3:o:microsoft:windows_10_21H2:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_10_21H2:*:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_11_21H2:*:*:*:*:*:*:arm64:* cpe:2.3:o:microsoft:windows_11_21H2:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_7:*:sp1:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_7:*:sp1:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_8.1:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_8.1:*:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_rt_8.1:*:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_server_2008_R2:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_server_2008_sp2:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_server_2008_sp2:*:*:*:*:*:*:x86:* cpe:2.3:o:microsoft:windows_server_2012:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_server_2012_R2:*:*:*:*:*:*:x64:* cpe:2.3:o:microsoft:windows_server_2016:*:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_server_2019:*:*:*:*:*:*:*:* cpe:2.3:o:microsoft:windows_server_2022:*:*:*:*:*:*:*:* |
|
Vendors & 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 11 21h2 Microsoft windows Server 2008 R2 Microsoft windows Server 2008 Sp2 Microsoft windows Server 2012 R2 |
|
Metrics |
cvssV3_1
|
MITRE
Status: PUBLISHED
Assigner: microsoft
Published: 2013-12-11T00:00:00
Updated: 2024-11-14T20:07:40.814Z
Reserved: 2013-06-03T00:00:00
Link: CVE-2013-3900
Vulnrichment
No data.
NVD
Status : Modified
Published: 2013-12-11T00:55:03.693
Modified: 2024-11-21T01:54:30.420
Link: CVE-2013-3900
Redhat
No data.