cve.bz

CVE-2020-1350 (SIGRed) Microsoft Windows DNS Server Remote Code Execution Vulnerability

10.0 criticalKEVEPSS 97%Fix available

Known as SIGRed

Critical (10.0) in Microsoft Windows. In CISA KEV since 2021-11-03. EPSS 97% estimated probability of exploitation activity in the next 30 days.

On this page
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'.

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
97% (unchanged from 97% a week ago; 97% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2021-11-03, due 2022-05-03
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2025-02-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-1350 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-1350?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-1350?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-1350 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
microsoft:windows_server_2008r2:sp1
microsoft:windows_server_2012r2

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET EXPLOIT Possible Windows DNS Integer Overflow Attempt M2 (CVE-2020-1350) sid 2030532
  • Emerging Threats Open ET EXPLOIT Possible Windows DNS Integer Overflow Attempt M1 (CVE-2020-1350) sid 2030533

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON