Cyber Resilience

CVE-2023-32020

Microsoft Windows Server 2008 r2

Published
14 June 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.0066 48th percentile
Risk Priority 52 floored blend · peak EPSS

Summary

CVE-2023-32020 is a medium-severity Reliance on Reverse DNS Resolution for a Security-Critical Action (CWE-350) vulnerability in Microsoft Windows Server 2008. Its CVSS base score is 5.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2023-32020 is a DNS spoofing vulnerability affecting the Windows DNS component. It carries a CVSS 3.1 base score of 5.6 and is associated with CWE-350, reflecting improper reliance on DNS for security decisions.

An unauthenticated remote attacker can exploit the flaw over the network without user interaction, though the attack requires high complexity. Successful exploitation allows limited impacts to confidentiality, integrity, and availability by spoofing DNS responses.

Microsoft has published an advisory for CVE-2023-32020 that includes patch availability and mitigation guidance; practitioners should consult the MSRC update guide for remediation steps specific to affected Windows versions.

The EPSS score rose from a low starting point to a peak of 0.0762 on 2025-01-22 before receding to the current value of 0.0119, indicating that exploitation interest emerged after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Windows DNS Spoofing Vulnerability

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1584.002 DNS Server Resource Development
Adversaries may compromise third-party DNS servers that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-30036Same product: Microsoft Windows Server 2008
CVE-2023-36395Same product: Microsoft Windows Server 2008
CVE-2023-35351Same product: Microsoft Windows Server 2008
CVE-2023-28306Same product: Microsoft Windows Server 2008
CVE-2023-28231Same product: Microsoft Windows Server 2008
CVE-2023-28305Same product: Microsoft Windows Server 2008
CVE-2023-35321Same product: Microsoft Windows Server 2008
CVE-2023-36706Same product: Microsoft Windows Server 2008
CVE-2023-28307Same product: Microsoft Windows Server 2008
CVE-2023-32033Same product: Microsoft Windows Server 2008

Affected Assets

microsoft
windows server 2008
all versions, r2
microsoft
windows server 2012
all versions, r2
microsoft
windows server 2016
all versions
microsoft
windows server 2019
all versions
microsoft
windows server 2022
all versions

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-03 mostly match
prevents

Strong authentication of users/services/hardware directly prevents security decisions based on unauthenticated reverse DNS.

DE.CM-01 partial match
prevents

Monitoring DNS services can detect adverse events stemming from unverified reverse lookups.

PR.IR-01 partial match
prevents

Network protections reduce the feasibility of attackers exploiting unauthenticated reverse-DNS decisions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

Network security controls can enforce authenticated, non-DNS-based host identification.

mitigates

Secure network services discourage use of unauthenticated reverse-DNS for access decisions.

prevents

Application security requirements can mandate authenticated host verification instead of reverse DNS.

prevents

Secure architecture principles discourage reliance on unauthenticated DNS for security decisions.

prevents

Secure coding practices can replace reverse-DNS checks with cryptographically verified identities.

prevents

Strong authentication mechanisms reduce reliance on unauthenticated DNS-based identity decisions.

References