Skip to content
Server Security Center
KEVcritical10.0

CVE-2020-1350: Microsoft Windows DNS Server Remote Code Execution

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CISA ADP)
10.0
critical
EPSS (exploit probability, 30 days)
97%
higher than 99.8% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2020-1350 explained

CVE-2020-1350 is a remote code execution vulnerability in Windows Domain Name System (DNS) servers, caused by improper handling of requests (CWE-20: Improper Input Validation). It affects multiple Microsoft Windows Server versions. CISA lists it as known to be exploited, so affected DNS servers need prompt patching.

Impact

An unauthenticated attacker can exploit the flaw over the network with low complexity and no user interaction. Successful exploitation can lead to remote code execution with high impact on confidentiality, integrity and availability, and the impact can extend beyond the DNS server component. CISA rates it as automatable, meaning it can be exploited at scale, with total technical impact. CISA also lists it as known to be exploited.

Who is affected

The CVE record lists Microsoft Windows Server 2008 R2 for x64-based Systems Service Pack 1, 2008 for 32-bit Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2, 2012, 2012 (Core installation), 2012 R2, 2012 R2 (Core installation) and 2016, plus 6 more items shown on this page. It also lists Windows Server, version 1909, 1903 and 2004 (Server Core installation). The CVE record names no fixed version.

Written with AI from the data on this page and checked against it automatically.

Official description

A remote code execution vulnerability exists in Windows Domain Name System servers when they fail to properly handle requests, aka 'Windows DNS Server Remote Code Execution Vulnerability'.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows Server
    Affected
    • 2008 R2 for x64-based Systems Service Pack 1
    • 2008 for 32-bit Systems Service Pack 2
    • 2008 for x64-based Systems Service Pack 2
    • 2012
    • 2012 (Core installation)
    • 2012 R2
    • 2012 R2 (Core installation)
    • 2016
    • 2016 (Core installation)
    • 2019
    • 2019 (Core installation)
    • 2008 for 32-bit Systems Service Pack 2 (Core installation)
    • 2008 for x64-based Systems Service Pack 2 (Core installation)
    • 2008 R2 for x64-based Systems Service Pack 1 (Core installation)
    Fixed in
    not stated
  • Microsoft Windows Server, version 1909 (Server Core installation)
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server, version 1903 (Server Core installation)
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

  • Microsoft Windows Server, version 2004 (Server Core installation)
    Affected
    –
    Fixed in
    not stated

    Affected versions are not specified in the CVE record.

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify all Windows Server systems running the DNS Server role.
  2. Apply the security updates from the Microsoft advisory for CVE-2020-1350, per CISA's required action.
  3. Prioritize internet-facing DNS servers and those reachable from untrusted networks.
  4. Restrict network access to DNS servers to trusted clients where possible.
  5. Check affected DNS servers for signs of compromise, since attackers are known to exploit this flaw.

The CVE record names no fixed version, which does not mean no fix exists. Follow the Microsoft advisory linked on this page to find the updates for each affected Windows Server version. CISA's required action is to apply updates per vendor instructions. Until updated, limit network exposure of DNS servers and monitor them for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-20 Improper Input Validation

Questions about CVE-2020-1350

Is CVE-2020-1350 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, with a US federal due date of 2022-05-03. Whether it is used in ransomware campaigns is listed as unknown.
Does an attacker need credentials or user interaction?
No. According to the CVSS data, the attack works over the network, needs no privileges and no user interaction, and has low complexity.
Which version fixes the vulnerability?
The CVE record does not name a fixed version. Check the Microsoft advisory for the updates that apply to your Windows Server version, and apply them as CISA requires.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.