CVE-2013-3900: WinVerifyTrust Signature Validation Vulnerability
Noroxi assessment
Priority: This week (action score 65/100)
- CISA has confirmed exploitation in the wild (Jan 10, 2022). Remediation deadline for US federal agencies: Jul 10, 2022.
- Probability of exploitation in the next 30 days: 44.6% (FIRST EPSS); higher than 98.7% of all records.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
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
- Published
- Dec 11, 2013
- Updated
- Oct 8, 2026
- EPSS
- 44.6% · 98th percentile
- CWE
- CWE-347
Report tools
Action score
65
Don’t wait for the next maintenance window.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 13 / 30 · 44.6%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · microsoft
- 5.5
- agree
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Jan 10, 2022. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Jul 10, 2022.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | windows 10 1507 | cpe:2.3:o:microsoft:windows_10_1507 |
| microsoft | windows 10 1607 | cpe:2.3:o:microsoft:windows_10_1607 |
| microsoft | windows 10 1809 | cpe:2.3:o:microsoft:windows_10_1809 |
| microsoft | windows 10 1909 | cpe:2.3:o:microsoft:windows_10_1909 |
| microsoft | windows 10 20h2 | cpe:2.3:o:microsoft:windows_10_20h2 |
| microsoft | windows 10 21h1 | cpe:2.3:o:microsoft:windows_10_21h1 |
| microsoft | windows 10 21h2 | cpe:2.3:o:microsoft:windows_10_21h2 |
| microsoft | windows 10 22h2 | cpe:2.3:o:microsoft:windows_10_22h2 |
| microsoft | windows 11 21h2 | cpe:2.3:o:microsoft:windows_11_21h2 |
| microsoft | windows 11 22h2 | cpe:2.3:o:microsoft:windows_11_22h2 |
| microsoft | windows 11 23h2 | cpe:2.3:o:microsoft:windows_11_23h2 |
| microsoft | windows 11 24h2 | cpe:2.3:o:microsoft:windows_11_24h2 |
and 10 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Windows 10 Version 1507
- N/Aaffected
Microsoft Windows 10 Version 1607
- N/Aaffected
Microsoft Windows 10 Version 1809
- N/A, N/Aaffected
Microsoft Windows 10 Version 21H2
- N/Aaffected
Microsoft Windows 10 Version 22H2
- N/Aaffected
Microsoft Windows 11 version 21H2
- N/Aaffected
Microsoft Windows 11 version 22H2
- N/Aaffected
Microsoft Windows 11 version 22H3
- N/Aaffected
Microsoft Windows 11 Version 23H2
- N/Aaffected
Microsoft Windows 11 Version 24H2
- N/Aaffected
Microsoft Windows Server 2008 Service Pack 2
- N/Aaffected
Microsoft Windows Server 2008 R2 Service Pack 1
- N/Aaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft windows 10 1507all versions
- microsoft windows 10 1607all versions
- microsoft windows 10 1809all versions
- microsoft windows 10 1909all versions
- microsoft windows 10 20h2all versions
- microsoft windows 10 21h1all versions
- microsoft windows 10 21h2all versions
- microsoft windows 10 22h2all versions
- microsoft windows 11 21h2all versions
- microsoft windows 11 22h2all versions
- microsoft windows 11 23h2all versions
- microsoft windows 11 24h2all versions
- microsoft windows 7all versions
- microsoft windows 8.1all versions
- microsoft windows rt 8.1all versions
- microsoft windows server 2008all versions
- microsoft windows server 2008r2
- microsoft windows server 2012all versions
- microsoft windows server 2012r2
- microsoft windows server 2016all versions
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34527Windows Print Spooler Remote Code Execution VulnerabilityKEV95Now
- CVE-2021-40444Microsoft MSHTML Remote Code Execution VulnerabilityKEV94Now
- CVE-2023-36025Windows SmartScreen Security Feature Bypass VulnerabilityKEV92Now
Published before and after this one in the same product
- Later →CVE-2015-2546Sep 8, 2015 · The kernel-mode driver in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows…KEV65This week
- Later →CVE-2015-6175Dec 9, 2015 · The kernel in Microsoft Windows 10 Gold allows local users to gain privileges via a crafted application, aka "Windows Kernel Memory…KEV63This week
- Later →CVE-2016-0099Mar 9, 2016 · The Secondary Logon Service in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server…KEV72This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Proof-of-concept repository on GitHub ×15
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 15 repositories | 2022-09-06 → 2026-07-19 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- CISA KEV+2952 d
- First PoC+3191 d
- TodayNov 16, 2026+4723 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
nvd-primary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.