Background
Windows Task Scheduler is a fundamental OS component that lets applications and system processes run scheduled jobs. Because it operates across privilege boundaries — low-privileged tasks can be created, but the scheduler itself runs at high privilege — it’s historically been a source of elevation of privilege bugs.
CVE-2024-49039 was patched in November 2024 and confirmed as actively exploited before the patch was available. Google’s Threat Analysis Group (TAG) attributed exploitation to RomCom, a Russia-linked threat actor (also tracked as Storm-0978/UNC2596), operating in campaigns against Ukrainian government and other European targets. This aligns with the concurrent CVE-2024-43451 exploitation by Russian groups in the same timeframe.
Technical Mechanism
The vulnerability is in the Windows Task Scheduler service and relates to how it handles certain RPC (Remote Procedure Call) calls from low-privilege contexts.
Specifically, the Task Scheduler exposes an RPC interface. Certain RPC methods that should only be callable from high-integrity processes can be invoked by a low-integrity process due to insufficient privilege checks. By calling these methods with crafted arguments, a low-privileged attacker can:
- Invoke a privileged RPC method in the Task Scheduler service
- The method executes in the context of the Task Scheduler’s service account (SYSTEM or equivalent)
- By manipulating the arguments (e.g., specifying a custom executable path), the attacker causes privileged code execution
The CVSS 8.8 score is notable for a local privilege escalation — the slightly higher-than-typical score reflects how easily this can be reached and how reliably it escalates privilege.
Real-World Exploitation Evidence
Google TAG’s analysis of the RomCom zero-day campaigns found:
- RomCom (Storm-0978 / UNC2596) — confirmed as the threat actor exploiting CVE-2024-49039 before the patch
- CVE-2024-9680 chained exploit — RomCom chained this Task Scheduler LPE with a Firefox use-after-free vulnerability (CVE-2024-9680) in a particularly sophisticated two-stage exploit
- Stage 1: Firefox UAF achieves code execution inside the Firefox renderer sandbox
- Stage 2: Task Scheduler LPE breaks out of the sandbox and escalates to SYSTEM
- No user interaction beyond browsing — the Firefox chain meant visiting a malicious page was sufficient for full SYSTEM compromise
- European government targeting — Ukrainian and other European government organisations were primary targets
This is the kind of exploit chain that traditionally required significant resources — a browser sandbox escape plus an OS LPE — suggesting RomCom is operating with substantial capability.
Impact Assessment
- SYSTEM code execution — from a sandboxed browser tab to OS-level access
- Security tool bypass — SYSTEM allows disabling AV/EDR
- Credential dumping — LSASS and SAM accessible at SYSTEM level
- Persistent access — SYSTEM can modify kernel and boot components
- Domain compromise path — from SYSTEM on a domain-joined machine, escalation to domain admin is straightforward
- State-sponsored espionage — in the context of the RomCom campaign, used for intelligence gathering against government targets
Affected Versions
| Product | Affected Versions | Fixed Version |
|---|---|---|
| Windows 10 (21H2, 22H2) | Before November 2024 patches | KB5046613 |
| Windows 11 (all versions) | Before November 2024 patches | KB5046617, KB5046633 |
| Windows Server 2019 | Before November 2024 patches | KB5046612 |
| Windows Server 2022 | Before November 2024 patches | KB5046616 |
Remediation Steps
- Apply November 2024 Patch Tuesday updates immediately
- Also apply Firefox patch for CVE-2024-9680 if Firefox is deployed — the chain requires both vulnerabilities
- Keep browsers updated — this exploit chain requires an unpatched browser for stage 1
- Consider enabling Windows Defender Exploit Guard Network Protection to block connections to known malicious infrastructure
- If RomCom activity is suspected:
- Look for indicators of RomCom tooling (check current threat intel feeds for hashes and infrastructure)
- Review network logs for connections to known RomCom C2 infrastructure
- Enable Windows Task Scheduler logging and audit for unexpected task operations
Detection Guidance
Windows Task Scheduler Logs:
- Event ID 4698: Scheduled task creation (look for tasks created by unexpected users)
- Event ID 4702: Scheduled task updated
Process monitoring — watch for SYSTEM-privileged processes spawned from unusual parents, particularly from browser-adjacent processes.
SIEM rule:
event_id = 4698 AND
task_created_by NOT IN (trusted_users_list) AND
task_run_as_user = "SYSTEM"
Network monitoring — RomCom C2 infrastructure (check current threat intelligence feeds for current indicators).
Suricata signature:
alert tcp $HOME_NET any -> any 443 (msg:"RomCom/Storm-0978 Possible C2 Related to CVE-2024-49039"; flow:established,to_server; tls.sni; pcre:"/[a-z]{8,15}\.(site|xyz|top|info)$/"; classtype:trojan-activity; sid:2034020; rev:1;)
Timeline
| Date | Event |
|---|---|
| 2024 (pre-patch) | RomCom exploits CVE-2024-49039 and CVE-2024-9680 as zero-days |
| October 2024 | Google TAG discovers the Firefox+Task Scheduler exploit chain |
| 9 October 2024 | Mozilla patches CVE-2024-9680 in Firefox 131.0.2 |
| 12 November 2024 | Microsoft patches CVE-2024-49039 in November Patch Tuesday |
| November 2024 | CISA adds to Known Exploited Vulnerabilities catalogue |
| November 2024 | Google TAG publishes detailed analysis of RomCom exploit chain |