Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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-29363 is a critical-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 20% 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.
CVE-2023-29363 is a remote code execution vulnerability in the Windows Pragmatic General Multicast (PGM) component. It carries a CVSS 3.1 score of 9.8 and is associated with CWE-122. The flaw permits unauthenticated network-based attacks that can result in complete confidentiality, integrity, and availability impacts on affected Windows systems.
An attacker can exploit the vulnerability over the network without credentials or user interaction to execute arbitrary code with the privileges of the vulnerable process, enabling full system compromise.
Microsoft security advisories addressing the issue are published at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-29363. The EPSS score for this CVE has remained low, moving only from 0.0556 to a peak of 0.0586.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-32936
Vulnerability Data
Windows Pragmatic General Multicast (PGM) 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.
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.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
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.