Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2020-1337: Windows Print Spooler Arbitrary File Write Privilege Escalation

Published Aug 17, 2020 · Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 mentions · peak 6 in a dayToday
CVSS7.8High · v3.1
EPSS14.2%97th percentile
CISA KEVNoNot listed
In the wildReported5 exploitation records in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2020-1337CWE-269

CVE-2020-1337 is a local elevation-of-privilege vulnerability in the Windows Print Spooler service. Improper handling of file-system writes allows an attacker logged on to an affected system to execute a specially crafted script or application and abuse arbitrary file writes to run code with SYSTEM privileges. The vulnerability crosses the security boundary between an ordinary user and the privileged service.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary code execution with SYSTEM privileges, compromising the affected host's confidentiality, integrity, and availability. An attacker can install programs, view, modify, or delete data, and create accounts with full user rights.

Mitigation

If you can’t patch tonight, do this now.

Restrict unnecessary local logon and script or application execution by untrusted users. Monitor for suspicious Print Spooler file creation and associated privilege-escalation activity. These are compensating controls rather than a replacement for patching; no vendor-confirmed workaround is specified.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update addressing CVE-2020-1337 for the affected Windows release, or a superseding cumulative update. The fix corrects how the Windows Print Spooler component writes to the file system. Specific update identifiers and affected release versions are not available in the supplied vulnerability details.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
cve_2020_1337_printerdemon.rbThis repository contains a single Metasploit module (Ruby file) that exploits CVE-2020-1337, a local privilege escalation vulnerability in the Microsoft Windows Print Spooler service. The exploit abuses a file write vulnerability to place a malicious DLL (ualapi.dll by default) in the system32 directory, which is then loaded by the Print Spooler service, granting SYSTEM privileges to the attacker. The module is highly configurable, allowing the user to specify custom paths and filenames, but defaults to targeting %WINDIR%\system32\ualapi.dll. The exploit is executed via a Meterpreter session and leverages PowerShell to run the attack script. The payload is a DLL generated by Metasploit, encoded in base64, and injected into the target system. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The main attack vector is local, requiring an existing session on the target machine. The module leaves artifacts on disk and may require a system reboot to complete the privilege escalation.Disclosed Nov 4, 2019 · Framework: metasploit · ruby · localWeaponizedCVE-2020-1337This repository is a C# proof-of-concept exploit for CVE-2020-1337, a Windows Print Spooler vulnerability that allows local privilege escalation by planting a malicious DLL into the protected C:\Windows\System32 directory. The exploit leverages Windows printer APIs and NT object manager tricks (junctions and symlinks) to bypass protections and write an arbitrary file to System32. The main logic is in Program.cs, which orchestrates the attack in two steps: (1) initializing the printer and sending a crafted print job, and (2) after a manual reboot, creating a mount point and symlink to redirect the print spooler to write the attacker-supplied file into System32. The exploit requires local access and the ability to reboot the system. The codebase is structured as a Visual Studio C# project, with core logic in Program.cs, Printer.cs (printer API interactions), and Utils.cs (mount point and symlink creation). The attack targets Windows 7 and later, specifically exploiting the Print Spooler service. No network endpoints are involved; all actions are performed locally. The exploit is operational as a proof-of-concept and requires a user-supplied payload (DLL or binary) to be planted.neofito · Disclosed Aug 11, 2020 · csharp · localPoCcve-2020-1337-pocThis repository is a proof-of-concept (POC) exploit for CVE-2020-1337, a Windows Print Spooler Elevation of Privilege vulnerability. The main code is in C++ and consists of a Visual Studio solution with two main source files: WerTrigger.cpp and TcpClient.cpp. WerTrigger.cpp orchestrates the exploit by creating a crafted Windows Error Reporting (WER) report file and directory, then triggers the Windows Error Reporting task to process it. After a short delay, it attempts to connect to a local TCP bind shell on 127.0.0.1:1337, which is expected to be spawned as a result of the exploit (typically by loading a malicious DLL). TcpClient.cpp implements the TCP client functionality for interacting with the shell. The exploit is local and targets vulnerable Windows systems. No external network endpoints are used; all actions are performed locally. The repository is structured as a Visual Studio C++ project and is intended for research and demonstration purposes.sailay1996 · Disclosed Aug 12, 2020 · cpp · localPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
FAQ

Frequently asked questions

Is CVE-2020-1337 exploited in the wild?
Yes. As of Nov 12, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-1337?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2020-1337, the earliest disclosed Nov 4, 2019.
Is there a patch for CVE-2020-1337?
Apply the Microsoft security update addressing CVE-2020-1337 for the affected Windows release, or a superseding cumulative update. The fix corrects how the Windows Print Spooler component writes to the file system.
What products are affected by CVE-2020-1337?
Microsoft Corporation Windows 10, Microsoft Corporation Windows 7, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Rt 8.1, Microsoft Corporation Windows Server 2008, and 3 more.
How severe is CVE-2020-1337?
CVE-2020-1337 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 14.2% (97th percentile) as of Nov 12, 2026.
Activity feed

Recent activity

9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
cryptika blogNews · Nov 12, 2026Hackers Abuse Windows Group Policy to Deploy Citrus Ransomware and Disable Microsoft Defender | Cryptika CybersecurityA vulnerability Citrus reportedly attempted to exploit in its ransomware operations, discussed in the context of escalating privileges after initial access. The article does not describe the flaw, identify its affected product, or confirm successful exploitation.Read more ↗cyber security newsNews · Nov 12, 2026Hackers Abuse Windows Group Policy to Deploy Citrus Ransomware and Disable Microsoft DefenderA vulnerability Citrus reportedly attempted to exploit during its post-compromise privilege-escalation activity. The content does not identify its affected product, explain its technical mechanism, or confirm successful exploitation. The separate mention of poorly configured 1C:Enterprise servers does not establish that they are affected by this CVE.Read more ↗malware newsNews · Nov 11, 2026Citrus Ransomware: VLESS for traffic, Sn00py for encryption, and LLMs lending a hand - Malware News - Malware Analysis, News and IndicatorsA Microsoft privilege-escalation vulnerability used in PowerShell scripts during a Citrus ransomware intrusion. The scripts were launched through an executable that investigators suspected was a Metasploit component. The reference does not confirm whether privilege escalation succeeded.Read more ↗securelistNews · Nov 11, 2026Citrus Ransomware: tactics, techniques, procedures, and links to Toy Ghouls | SecurelistA vulnerability used in the privilege-escalation stage of a Citrus ransomware intrusion. Attackers launched PowerShell scripts containing the exploit through an executable suspected to be a Metasploit component. The article identifies publicly available exploit code but does not describe the vulnerability's underlying mechanism or confirm successful privilege escalation.Read more ↗
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence5Every report linking this CVE to a named adversary.
Associated malware3Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.