dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 5 Apr 2022. Known ransomware use
Windows 10 1507Operating system · Microsoft

CVE-2019-1069

HIGH · 7.8 CVSS v3.1 Published 2019-06-12
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
In the wild Ransomware Public exploit Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An elevation of privilege vulnerability exists in the Windows Task Scheduler service that incorrectly validates certain file operations. An attacker with the ability to execute unprivileged code on a targeted system can exploit improper file operation validation to gain elevated system privileges.

MitigationApply the Microsoft security update for CVE-2019-1069, which corrects file operation validation in the Task Scheduler service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:all versions
Windows 10 1607Operating system
Affected:all versions
Windows 10 1703Operating system
Affected:all versions
Windows 10 1709Operating system
Affected:all versions
Windows 10 1803Operating system
Affected:all versions
Windows 10 1809Operating system
Affected:all versions
Windows 10 1903Operating system
Affected:all versions
Windows Server 1803Operating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version
    Run 'winver' or 'systeminfo' from command prompt and note the version number and build
    Affected if The version displayed matches Windows 10 1507, 1607, 1703, 1709, 1803, 1809, 1903, or Windows Server 1803 (any build)
  2. Confirm Task Scheduler service status
    Run 'sc query schedule' from command prompt to check if the Task Scheduler service is running
    Affected if The service is running and accessible to the current user account
  3. Verify current user privileges
    Run 'whoami /priv' to list current user privileges
    Affected if The user has limited privileges but has the ability to create or modify scheduled tasks
  4. Check for applied security update
    Run 'wmic qfe get hotfixid,installedon' or check Windows Update history for security update KB4507453 (June 2019)
    Affected if The security update KB4507453 is NOT installed on the system

The system is vulnerable if it runs any affected Windows 10 or Windows Server 1803 version AND lacks the KB4507453 security update, allowing a low-privilege user to potentially elevate via Task Scheduler file operation exploitation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2019-1069, which corrects file operation validation in the Task Scheduler service.

Recommended fix High confidence

For Windows 10 1507 (end of support), upgrade to a supported Windows 10 version (1909 or later) or migrate to Windows 11; for all other affected versions, apply the relevant Microsoft security update from Windows Update or the Microsoft Update Catalog

  1. Open Windows Update settings on the affected Windows system
  2. Check for and install all available Windows security updates
  3. Verify that the update for CVE-2019-1069 (MSRC security update) is installed by checking the installed updates list
  4. Restart the system if prompted to complete the installation
  5. Confirm the vulnerability is mitigated by verifying the Task Scheduler service has been updated
Caveat Ensure compatibility testing is performed on legacy systems before applying updates, as some older configurations may have dependencies affected by the security changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1069 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1069 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data