Is CVE-2013-3900 exploited in the wild?

Yes. CVE-2013-3900 is known to be exploited in the wild, first recorded on 10 January 2022. Treat it as urgent.

How severe is CVE-2013-3900?

Critical severity, with a CVSS score of 8.8, published 10 January 2022.

Which products and versions are affected?

Microsoft Windows 10 All currently supported versions; Microsoft Windows 11 All currently supported versions; Microsoft Windows Server 2008 SP2, R2 SP1; Microsoft Windows 7 SP1; and 5 more.

Is there a fix for CVE-2013-3900?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2013-3900 attacked?

It is attacked over the network, in an operating system.

Am I affected by CVE-2013-3900?

Check whether you run Microsoft WinVerifyTrust Function. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2013-3900: Microsoft WinVerifyTrust function Remote Code Execution

CVE-2013-3900 · Severity: critical · CVSS 8.8 · Exploited in the wild · Published 2022-01-10

A remote code execution vulnerability exists in the WinVerifyTrust function's handling of Windows Authenticode signature verification for Portable Executable (PE) files. An attacker can modify a signed executable to include malicious code in unverified portions of the file without invalidating the digital signature. Successful exploitation requires a user to run or install a specially crafted, signed PE file, potentially granting the attacker complete control over the affected system.

Vendors: Microsoft.

Quick answers

Is CVE-2013-3900 exploited in the wild?: Yes. CVE-2013-3900 is known to be exploited in the wild, first recorded on 10 January 2022. Treat it as urgent.
How severe is CVE-2013-3900?: Critical severity, with a CVSS score of 8.8, published 10 January 2022.
Which products and versions are affected?: Microsoft Windows 10 All currently supported versions; Microsoft Windows 11 All currently supported versions; Microsoft Windows Server 2008 SP2, R2 SP1; Microsoft Windows 7 SP1; and 5 more.
Is there a fix for CVE-2013-3900?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2013-3900 attacked?: It is attacked over the network, in an operating system.
Am I affected by CVE-2013-3900?: Check whether you run Microsoft WinVerifyTrust Function. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

Microsoft Windows 10 All currently supported versions
Microsoft Windows 11 All currently supported versions
Microsoft Windows Server 2008 SP2, R2 SP1
Microsoft Windows 7 SP1
Microsoft Windows 8.1
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2016
Microsoft Windows Server 2019
Microsoft Windows Server 2022

Timeline

2013-12-10: disclosed: Original publication of MS13-098 and CVE-2013-3900
2022-01-10: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
2022-01-10: advisory: Republished by Microsoft to update supported Windows versions and configuration guidance

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.