CVE-2020-1337: Windows Print Spooler Elevation of Privilege Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

An elevation of privilege vulnerability exists when the Windows Print Spooler service improperly allows arbitrary writing to the file system. An attacker who successfully exploited this vulnerability could run arbitrary code with elevated system privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted script or application. The update addresses the vulnerability by correcting how the Windows Print Spooler Component writes to the file system.

Description quoted from the CVE record (assigned by microsoft, published 2020-08-17).

How it can be exploited

Exploitable with local access with low attack complexity needing low privileges and no user interaction. Impact: 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/E:P/RL:O/RC:C

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 1 Metasploit module, 6 code repositories and 2 research write-ups naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 15 references on Exploit Observer

Live scores

EPSS
0.142
likely to be attacked soon
VEDAS
0.989
strong exploit evidence
On CISA KEV
Not listed
Detection rule
No public rule yet

Who is affected

ProductAffectedNot affected
Microsoft Windows 10 Version 2004from 10.0.0 before publicationNot stated
Microsoft Windows Server version 2004from 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1803from 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1809from 10.0.0 before publicationNot stated
Microsoft Windows Server 2019from 10.0.0 before publicationNot stated
Microsoft Windows Server 2019 (Server Core installation)from 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1909from 10.0.0 before publicationNot stated
Microsoft Windows Server, version 1909 (Server Core installation)from 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1709 for 32-bit Systemsfrom 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1709from 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1903 for 32-bit Systemsfrom 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1903 for x64-based Systemsfrom 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1903 for ARM64-based Systemsfrom 10.0.0 before publicationNot stated
Microsoft Windows Server, version 1903 (Server Core installation)from 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1507from 10.0.0 before publicationNot stated
Microsoft Windows 10 Version 1607from 10.0.0 before publicationNot stated
Microsoft Windows Server 2016from 10.0.0 before publicationNot stated
Microsoft Windows Server 2016 (Server Core installation)from 10.0.0 before publicationNot stated
Microsoft Windows 7from 6.1.0 before publicationNot stated
Microsoft Windows 7 Service Pack 1from 6.1.0 before publicationNot stated

10 more products are listed in the CVE record.

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Fixed versions stated in the CVE record: publication.

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

Advisories on this CVE

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust