Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2023-28311 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Microsoft 365 Apps. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 15% 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.
Microsoft Word contains a remote code execution vulnerability tracked as CVE-2023-28311 that stems from a heap-based buffer overflow, tracked under CWE-122. The flaw affects Microsoft Word and carries a CVSS 3.1 score of 7.8 with an attack vector that requires an attacker to supply a malicious file that the victim opens locally.
An unauthenticated attacker can exploit the issue by convincing a user to open a specially crafted document, after which arbitrary code executes with the privileges of the current user, resulting in full confidentiality, integrity, and availability impact on the affected system.
Microsoft security advisories hosted at the MSRC update guide for CVE-2023-28311 describe available patches and mitigation steps for supported versions of Word. The associated EPSS score rose from low values after disclosure to a peak of 0.1017 in January 2025 before receding to the current 0.0835, indicating a later surge in exploitation interest that warrants renewed attention.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-32018
Vulnerability Data
Microsoft Word 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.
Change management ensures controlled deployment of fixes for discovered heap-overflow vulnerabilities.