Microsoft · WinVerifyTrust function · CWE-20 · published 2013-12-11

CVE-2013-3900Microsoft WinVerifyTrust function Remote Code Execution

This week Known exploited in the wild.

CVE-2013-3900 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2022-01-10. EPSS estimates a 44.6% chance of exploitation in the next 30 days, higher than 98% of all CVEs. This WinVerifyTrust function vulnerability: CVSS 5.5 (v3.1). CISA’s required action: Apply updates per vendor instructions. US federal agencies must remediate by 2022-07-10. Patch this week.

Share this

Remediation#

CISA required action: Apply updates per vendor instructions. (federal due date 2022-07-10)

Patch events

  1. This weekExploited (KEV)CISA due 2022-07-10

    Operating systemMicrosoft WinVerifyTrust function

    Remote Code ExecutionCVE-2013-3900

    Why: Known exploited in the wild.

Exploit intelligence#

SignalValueSource
Known exploitedYes, added 2022-01-10CISA KEV
Ransomware useUnknownCISA KEV
EPSS (30-day exploitation probability)45% (99th pct)FIRST EPSS v2026.06.15
CVSS base score5.5 (v3.1)
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
CNA / CISA ADP
SSVC exploitationactiveCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Weakness: CWE-20: Improper Input Validation

More from this vendor: all Microsoft vulnerabilities · recent KEV additions

Affected versions (from the CVE record)#

Description (from the CVE record)#

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

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →