Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-36425 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 28% of CVEs by exploit likelihood; 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.
Windows Distributed File System (DFS) contains a remote code execution vulnerability tracked as CVE-2023-36425. The flaw affects the Windows DFS component and carries a CVSS 3.1 score of 8.0, reflecting network attack vector, high attack complexity, required high privileges, no user interaction, changed scope, and full impact on confidentiality, integrity, and availability. The associated weakness is listed under CWE-122.
An attacker must possess high privileges and overcome high complexity conditions to exploit the issue over the network. Successful exploitation grants the ability to execute arbitrary code, with the changed scope allowing impact beyond the initially vulnerable component.
Microsoft has published guidance for the vulnerability through its Security Response Center at the listed MSRC advisory URL. The EPSS score remained low for an extended period after disclosure but rose materially to a peak of 0.0636 on 2025-01-22 before receding, indicating a period of increased exploitation interest that warrants attention.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-40390
Vulnerability Data
Windows Distributed File System (DFS) Remote Code Execution Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
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.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.
Timely patching removes known heap-overflow instances after they exist.
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.
Security testing in development and acceptance can detect heap overflows before release.
Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.
Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.
Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.
Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.