Skip to content
Fencer Intel
critical 10.0

CVE-2020-1350 kev in the critical feed json

A remote code execution vulnerability exists in Windows Domain Name System servers when they fail to properly handle requests, aka 'Windows…

published 6y ago modified 4mo ago also EUVD-2020-12226

cvss
10.0
version 3.1, CNA
cisa kev
Exploited
added 2021-11-03
epss
96.7%
EPSS 96.7% chance of exploitation in 30 days, percentile 99.8%
public exploits
0
none known

Summary

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'.

Patch / fix

cisa required action Apply updates per vendor instructions.

Is CVE-2020-1350 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. Added to CISA KEV
  3. CISA patch deadline
  4. CISA SSVC: exploitation active

Known exploited

Added
5y ago
Patch by
2022-05-03 (4y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions.
Vendor, product
Microsoft, Windows
CISA name
Microsoft Windows DNS Server Remote Code Execution Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

96.72% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • Microsoft Windows Server
  • Microsoft Windows Server, version 1909 (Server Core installation)
  • Microsoft Windows Server, version 1903 (Server Core installation)
  • Microsoft Windows Server, version 2004 (Server Core installation)

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.