Skip to main content
Mallory
MediumExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2013-3900: Windows WinVerifyTrust Signature Validation Vulnerability

Published Dec 11, 2013 · Updated 18 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS44.6%99th percentile
CISA KEVYesAdded Jan 10, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2013-3900CWE-347 · Improper Verification of…

CVE-2013-3900 is an Authenticode signature-verification vulnerability in the Microsoft Windows WinVerifyTrust function. Insufficient validation of portable executable (PE) certificate data allows an attacker to add malicious code or other data to unverified portions of an existing signed executable without invalidating its apparent signature. Exploitation requires a user or application to run or install a specially crafted signed PE file, with an execution mechanism that processes the embedded malicious content. Successful exploitation permits code execution with the privileges of the launching context. Microsoft's stricter signature-verification behavior remains opt-in, including on Windows 10 and Windows 11.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Attackers can conceal malicious payloads in apparently trusted signed binaries, undermining security decisions that rely on Authenticode signature validity. Successful execution can compromise confidentiality, integrity, and availability within the launching account's permissions. Execution with administrative privileges can permit complete system compromise, including software installation, data access or destruction, and creation of privileged accounts. Exploitation has been observed in Zloader infections, the 3CX supply-chain attack, and espionage malware loaders.

Mitigation

If you can’t patch tonight, do this now.

Use least-privileged accounts to limit the consequences of malicious code execution. Restrict execution of untrusted installers and downloaded executables, and do not treat a valid digital signature as sufficient evidence of safety. Where operationally feasible, disable or restrict mshta.exe to disrupt documented script-execution chains abusing signed PE files; this does not address every exploitation mechanism.

Remediation

Patch, then assume compromise.

For affected legacy Windows releases, install the applicable MS13-098 security update, KB2893294, and enable stricter Authenticode verification. Windows 10 and Windows 11 already incorporate the supporting code and require configuration rather than a separate update for this feature. Set EnableCertPaddingCheck to 1 under HKLM\Software\Microsoft\Cryptography\Wintrust\Config and, on 64-bit systems, also under HKLM\Software\Wow6432Node\Microsoft\Cryptography\Wintrust\Config, following Microsoft's current configuration guidance. Installing the update alone does not enable enforcement. Test compatibility before deployment: stricter verification treats nonconforming signed binaries as unsigned and may affect installers. Software publishers should ensure installers extract executable content only from validated portions of signed files.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 11 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2013-3900-PowerShell-PoCThis repository is a small standalone PowerShell proof-of-concept for CVE-2013-3900, the Windows Authenticode certificate padding issue. It is not part of a larger exploit framework. The repository contains four files: the main PowerShell PoC, a README explaining the vulnerability and usage, a .reg remediation file that enables EnableCertPaddingCheck, and a license file. The main script, CVE-2013-3900-PoC-padding-injection.ps1, operates entirely locally on PE files. It takes an input executable, verifies that it has a valid embedded Authenticode signature, parses the PE header to locate DataDirectory[4] (the Certificate Table), reads the first WIN_CERTIFICATE structure, inserts attacker-controlled padding bytes into the certificate blob, updates the certificate length metadata, and writes out a modified executable. The default padding is 4096 bytes of 0x41. After modification, it checks the resulting file with both Get-AuthenticodeSignature and a direct P/Invoke call to WinVerifyTrust from wintrust.dll using the generic verification GUID. This lets the operator observe whether the host still trusts the tampered file under current policy. The exploit capability is therefore simulation and validation of the CVE-2013-3900 condition, not remote compromise or code execution. It demonstrates how a signed PE can be altered in its certificate area while potentially retaining a trusted status on systems where strict padding checks are disabled. The included remediation-64bit-win.reg file sets EnableCertPaddingCheck=1 in both native and Wow6432Node Wintrust registry paths, which causes modified files with extra certificate padding to be rejected. There are no network callbacks, C2 endpoints, or remote targets in the code. The only fingerprintable artifacts are local file paths, the Wintrust DLL/API usage, the verification GUID, and the registry keys used for remediation. Overall, this is a legitimate educational PoC and local test harness for assessing whether a Windows system remains susceptible to the Authenticode padding behavior associated with CVE-2013-3900.norvethil · Disclosed Aug 18, 2025 · powershell · markdown · local · filePoCCVE-2013-3900-PowerShell-PoCThis repository provides a PowerShell proof-of-concept (PoC) exploit for CVE-2013-3900, a vulnerability in the Windows Authenticode signature validation process. The main script, 'CVE-2013-3900-PoC-padding-injection.ps1', takes a signed PE file (by default, MSBuild.exe), injects artificial padding into its certificate section, and saves a modified copy. It then checks the digital signature status of both the original and modified files using Authenticode and the WinVerifyTrust API, demonstrating whether the system accepts or rejects the altered file. The exploit shows that, on unpatched systems, the signature remains valid even after modification, highlighting the risk of malicious code injection into signed binaries. The repository also includes a registry file ('remediation-64bit-win.reg') to enable the mitigation (EnableCertPaddingCheck=1), which causes Windows to reject such tampered files. The README provides context, usage instructions, and a link to the official Microsoft advisory. The repository is structured for educational and research purposes, with clear separation between the exploit script, documentation, and mitigation instructions.PREN0MEN · Disclosed Aug 18, 2025 · powershell · reg · localPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 1909operating_system
Microsoft CorporationWindows 10 20h2operating_system
Microsoft CorporationWindows 10 21h1operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 21h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
FAQ

Frequently asked questions

Is CVE-2013-3900 exploited in the wild?
Yes. As of Oct 30, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Jan 10, 2022.
Is there a public exploit for CVE-2013-3900?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2013-3900, the earliest disclosed Aug 18, 2025.
Is there a patch for CVE-2013-3900?
For affected legacy Windows releases, install the applicable MS13-098 security update, KB2893294, and enable stricter Authenticode verification. Windows 10 and Windows 11 already incorporate the supporting code and require configuration rather than a separate update for this feature.
What products are affected by CVE-2013-3900?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 1909, Microsoft Corporation Windows 10 20h2, and at least 17 more.
How severe is CVE-2013-3900?
CVE-2013-3900 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 44.6% (99th percentile) as of Oct 30, 2026.
Activity feed

Recent activity

18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
codebyNews · Oct 7, 2026SilverFox BYOVD: обход антивируса невидимым драйверомAn improper cryptographic signature-verification vulnerability in WinVerifyTrust that allows modification of a signed PE file without invalidating its signature. The article reports CVSS 5.5, CISA KEV inclusion, and exploitation observed since November 2021. It discusses the flaw in relation to hash-based detection evasion, without explicitly establishing that Silver Fox exploited this specific CVE.Read more ↗codebyNews · Jun 11, 2026Детальный разбор цифровых подписей РЕ-файловA Windows Authenticode/WinVerifyTrust signature validation flaw that can allow extra data to be appended to a signed PE file without invalidating the signature unless stricter certificate padding checks are enabled.Read more ↗alyac blogNews · Jun 1, 2026디지털 서명 검증을 우회하는 MS Word 변조 악성코드 주의 (CVE-2013-3900)Windows Authenticode 검증의 구조적 특성을 악용해 PE 파일의 인증서 테이블 뒤에 임의 데이터를 삽입해도 디지털 서명이 유효하게 유지되도록 만드는 취약점으로, 신뢰 기반 보안 통제를 우회하는 데 사용된다.Read more ↗sophos threat researchNews · Jan 1, 2026Zloader Installs Remote Access Backdoors and Delivers Cobalt Strike | SOPHOSA known Windows vulnerability that allows malicious script content to be appended to Microsoft-signed files and then executed, in this case via mshta.exe, to aid Zloader delivery and defense evasion.Read more ↗
+10 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence4Every report linking this CVE to a named adversary.
Associated malware13Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.