CVE-2022-44667HighCVSS 7.8

Windows Media Remote Code Execution Vulnerability

Published
December 13, 2022
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2022-44667 →

📋 Description

According to the CVSS metric, the attack vector is local (AV:L). Why does the CVE title indicate that this is a remote code execution? The word Remote in the title refers to the location of the attacker. This type of exploit is sometimes referred to as Arbitrary Code Execution (ACE). The attack itself is carried out locally. The vulnerable endpoint is only available over the local VM interface as all external communication is blocked. This means an attacker needs to execute code from the local machine to exploit the vulnerability.

According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do? Exploitation of the vulnerability requires that a user open a specially crafted file. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) containing a specially crafted file designed to exploit the vulnerability. An attacker would have no way to force users to visit the website. Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an email or instant message, and then convince them to open the specially crafted file.

🎯 Affected products39

  • Windows 10 Version 1607 for 32-bit Systems
  • Windows 10 Version 1607 for x64-based Systems
  • Windows 10 Version 1809 for 32-bit Systems
  • Windows 10 Version 1809 for ARM64-based Systems
  • Windows 10 Version 1809 for x64-based Systems
  • Windows 10 Version 20H2 for 32-bit Systems
  • Windows 10 Version 20H2 for ARM64-based Systems
  • Windows 10 Version 21H1 for 32-bit Systems
  • Windows 10 Version 21H1 for ARM64-based Systems
  • Windows 10 Version 21H1 for x64-based Systems
  • Windows 10 Version 21H2 for 32-bit Systems
  • Windows 10 Version 21H2 for ARM64-based Systems
  • Windows 10 Version 21H2 for x64-based Systems
  • Windows 10 Version 22H2 for 32-bit Systems
  • Windows 10 Version 22H2 for ARM64-based Systems
  • Windows 10 Version 22H2 for x64-based Systems
  • Windows 10 for 32-bit Systems
  • Windows 10 for x64-based Systems
  • Windows 11 Version 22H2 for ARM64-based Systems
  • Windows 11 Version 22H2 for x64-based Systems
  • Windows 11 version 21H2 for ARM64-based Systems
  • Windows 11 version 21H2 for x64-based Systems
  • Windows 7 for 32-bit Systems Service Pack 1
  • Windows 7 for x64-based Systems Service Pack 1
  • Windows 8.1 for 32-bit systems
  • Windows 8.1 for x64-based systems
  • Windows RT 8.1
  • Windows Server 2008 R2 for x64-based Systems Service Pack 1
  • Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
  • Windows Server 2012
  • +9 more not shown

✅ Remediation

KB5021237 (Security Update) — fixed build 10.0.17763.3770 KB5021233 (Security Update) — fixed build 10.0.19043.2364 KB5021249 (Security Update) — fixed build 10.0.20348.1366 KB5021233 (Security Update) — fixed build 10.0.19042.2364 KB5021234 (Security Update) — fixed build 10.0.22000.1335 KB5021233 (Security Update) — fixed build 10.0.19044.2364 KB5021255 (Security Update) — fixed build 10.0.22621.993 KB5021233 (Security Update) — fixed build 10.0.19045.2364 KB5021243 (Security Update) — fixed build 10.0.10240.19624 KB5021235 (Security Update) — fixed build 10.0.14393.5582 KB5021291 (Monthly Rollup) — fixed build 6.1.7601.26266 KB5021288 (Security Only) — fixed build 6.1.7601.26266 KB5021294 (Monthly Rollup) — fixed build 6.3.9600.20721 KB5021296 (Security Only) — fixed build 6.3.9600.20721 KB5021285 (Monthly Rollup) — fixed build 6.2.9200.24018 KB5021303 (Security Only) — fixed build 6.2.9200.24018

🔗 References (28)