Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2014-1761 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Microsoft Word. 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 0.5% 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 Word 2003 SP3 through 2013, Word Viewer, Office Compatibility Pack SP3, Office for Mac 2011, Word Automation Services on SharePoint Server 2010 and 2013, and Office Web Apps 2010 and 2013 are affected by an out-of-bounds write vulnerability (CWE-787) that can be triggered by specially crafted RTF data. The flaw permits memory corruption that may result in either arbitrary code execution or a denial of service condition. The issue received a CVSS 3.1 score of 7.8 and was publicly disclosed on 25 March 2014.
An attacker can deliver the malicious RTF content through a crafted document that a user opens locally or that is processed by server-side components such as Word Automation Services or Office Web Apps. Successful exploitation grants the attacker the ability to run arbitrary code in the context of the current user or to crash the affected process, with no privileges required beyond convincing the target to handle the file.
Microsoft security bulletin MS14-017 and the associated advisory 2953095 address the vulnerability through cumulative updates for the listed products. The bulletin recommends applying the patches as the primary mitigation and notes that the flaw had already been exploited in targeted attacks at the time of release.
The vulnerability appears in the CISA Known Exploited Vulnerabilities catalog, confirming continued real-world exploitation since its initial use in March 2014.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2014-1835
Vulnerability Data
Microsoft Word 2003 SP3, 2007 SP3, 2010 SP1 and SP2, 2013, and 2013 RT; Word Viewer; Office Compatibility Pack SP3; Office for Mac 2011; Word Automation Services on SharePoint Server 2010 SP1 and SP2 and 2013; Office Web Apps 2010…
more
SP1 and SP2; and Office Web Apps Server 2013 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted RTF data, as exploited in the wild in March 2014.
- CWE(s)
- KEV Date Added
- 15 February 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
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 (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
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 and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.