CVE-2023-21741
Memory Safety in Microsoft Visio 2013 … 2016
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:LSummary
CVE-2023-21741 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Microsoft Visio. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 24% 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-21741 is an information disclosure vulnerability in Microsoft Office Visio stemming from an out-of-bounds read condition (CWE-125). It carries a CVSS 3.1 base score of 7.1 reflecting network attack vector, low complexity, low privileges required, and no user interaction, resulting in high confidentiality impact together with limited availability consequences.
An authenticated attacker positioned on the network can send a specially crafted Visio file or session to the affected application and obtain sensitive information from memory without any user interaction, while also inducing a partial denial-of-service condition.
The official Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-21741 supplies patch guidance and should be consulted for remediation steps. Exploitation probability remains low, with an EPSS score of 0.0644 that has shown no material increase since disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-25908
Vulnerability Data
Microsoft Office Visio Information Disclosure Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
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.
Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.
Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.
Routine patching replaces vulnerable code containing out-of-bounds read flaws.
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 includes fuzzing and static analysis that detect out-of-bounds read defects before release.
Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.
Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.
Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.
Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.
Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.