Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2015-1770 is a high-severity Access of Uninitialized Pointer (CWE-824) vulnerability in Microsoft Office. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities 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 Office 2013 SP1 and 2013 RT SP1 contain an uninitialized memory use vulnerability, identified as CVE-2015-1770 and assigned CWE-824, that permits remote code execution when a crafted Office document is processed. The flaw received a CVSS 3.1 base score of 8.8 reflecting network attack vector, low attack complexity, no required privileges, and required user interaction.
An attacker can deliver the malicious document through typical channels such as email or web downloads; successful exploitation grants arbitrary code execution on the target system, with high impact to confidentiality, integrity, and availability.
Microsoft security bulletin MS15-059 describes the issue and supplies the corresponding security updates for affected Office installations.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2015-1900
Vulnerability Data
Microsoft Office 2013 SP1 and 2013 RT SP1 allows remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Uninitialized Memory Use Vulnerability."
- CWE(s)
- KEV Date Added
- 28 March 2022
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 SDLC practices directly prevent uninitialized pointer bugs via coding standards, analysis, and reviews, but eliminating this single weakness only partially fulfills the broader control.
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 can detect uninitialized pointer usage before release.
Secure development life cycle mandates practices that reduce uninitialized pointer defects.
Application security requirements can specify pointer initialization rules.
Secure architecture principles discourage unsafe pointer handling.
Secure coding standards directly prohibit use of uninitialized pointers.