CVE-2013-3900
What it is
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
At a glance
- Exploitability
- Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data tampering.
- In the wild
- CISA lists this as exploited in real attacks. Treat as urgent.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- 2022-01-10 Exploited in the wildAdded to CISA's Known Exploited Vulnerabilities list
- 2022-07-10 Remediation deadlineCISA's due date for federal agencies to fix it
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: yes, CISA lists it. This puts it above everything that is not.
- Exploit odds: 44.6% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Added to CISA KEV
- 2022-01-10
- Exploit probability
- 44.6% · EPSS, next 30 days
- Weakness
- CWE-347
- Record status
- Analyzed
Affected
- 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 10 22h2
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2013-3900.md and follow it. Check whether this project is affected by CVE-2013-3900. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2013/ms13-098
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
- http://blogs.technet.com/b/srd/archive/2013/12/10/ms13-098-update-to-enhance-the-security-of-authenticode.aspx
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2013/ms13-098
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2013-3900