cve.bz

CVE-2019-1069 Microsoft Task Scheduler Privilege Escalation Vulnerability

7.8 highKEVExploit referenceEPSS 6.2%Fix available

High (7.8) in Microsoft Task Scheduler. In CISA KEV since 2022-03-15, with known ransomware use. EPSS 6.2% estimated probability of exploitation activity in the next 30 days.

On this page
An elevation of privilege vulnerability exists in the way the Task Scheduler Service validates certain file operations. An attacker who successfully exploited the vulnerability could gain elevated privileges on a victim system. To exploit the vulnerability, an attacker would require unprivileged code execution on a victim system. The security update addresses the vulnerability by correctly validating file operations.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
6.2% (unchanged from 6.2% a week ago; 6.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 94th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-03-15, due 2022-04-05, known ransomware use
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2022-03-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-1069 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-1069?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-1069?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-1069 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1703from 10.0.0 before publication
Microsoft Windows 10 Version 1803from 10.0.0 before publication
Microsoft Windows Server, version 1803 (Server Core Installation)from 10.0.0 before publication
Microsoft Windows 10 Version 1809from 10.0.17763.0 before publication
Microsoft Windows 10 Version 1809from 10.0.0 before publication
Microsoft Windows Server 2019from 10.0.17763.0 before publication
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before publication
Microsoft Windows 10 Version 1709 for 32-bit Systemsfrom 10.0.0 before publication
Microsoft Windows 10 Version 1709from 10.0.0 before publication
Microsoft Windows 10 Version 1903 for 32-bit Systemsfrom 10.0.0 before publication
Microsoft Windows 10 Version 1903 for x64-based Systemsfrom 10.0.0 before publication
Microsoft Windows 10 Version 1903 for ARM64-based Systemsfrom 10.0.0 before publication
Microsoft Windows Server, version 1903 (Server Core installation)from 10.0.0 before publication
Microsoft Windows 10 Version 1507from 10.0.10240.0 before publication
Microsoft Windows 10 Version 1607from 10.0.14393.0 before publication
Microsoft Windows Server 2016from 10.0.14393.0 before publication
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before publication

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON