CVE-2022-44698
Published: December 13, 2022
Official Description
Microsoft Defender SmartScreen contains a security feature bypass vulnerability that could allow an attacker to evade Mark of the Web (MOTW) defenses via a specially crafted malicious file.
CISA KEV Advisory
Microsoft Defender SmartScreen Security Feature Bypass Vulnerability
Microsoft Defender SmartScreen contains a security feature bypass vulnerability that could allow an attacker to evade Mark of the Web (MOTW) defenses via a specially crafted malicious file.
Apply updates per vendor instructions.
Risk Analysis
This Microsoft Defender SmartScreen vulnerability allows an attacker to bypass Mark of the Web (MOTW) defenses using a specially crafted malicious file. This flaw poses a significant risk as it can enable the execution of untrusted content. The high EPSS score of 0.66423 and its inclusion in CISA's KEV confirm active exploitation.
Active exploitation of this vulnerability has been observed in the wild. Attackers can remotely bypass security features using malicious files.
Apply all available security updates for Microsoft Defender SmartScreen. Educate users about the risks of opening suspicious files, even if they appear to bypass security warnings.
Technical Analysis
CVE-2022-44698 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2022-44698 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (2)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2022-44698 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1