CVE-2015-1642: Microsoft Office Memory Corruption
Microsoft Office · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-03.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 53%
- higher than 99% of all CVEs
- Added to CISA KEV
- 2022-03-03
- US federal due date 2022-03-24
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2015-1642 explained
CVE-2015-1642 is a memory corruption flaw (out-of-bounds write) in Microsoft Office. A crafted document can let remote attackers execute arbitrary code. CISA lists it as known to be exploited, so systems still running affected Office versions face real risk.
Impact
An attacker who convinces a user to open a crafted document can run arbitrary code on the system. No privileges are needed, but user interaction is required. CISA rates the technical impact as total, meaning full control of the affected component, with high impact on confidentiality, integrity and availability. CISA does not consider it automatable, so attacks need manual steps such as delivering the document. Attackers are known to use this vulnerability.
Who is affected
The description names Microsoft Office 2007 SP3, 2010 SP2 and 2013 SP1. The CVE record itself lists no structured affected versions for Microsoft Office. The record names no fixed version either. Consult the Microsoft advisory for the updates that address this issue.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Office 2007 SP3, 2010 SP2, and 2013 SP1 allows remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office Memory Corruption Vulnerability."
CISA required action: Apply updates per vendor instructions.
CISA notes
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: docs.microsoft.com/en-us/security-updates/securitybulleti…
- CISA's deadline for US federal agencies: 2022-03-24 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for this vulnerability per the vendor advisory.
- Confirm that all Office 2007 SP3, 2010 SP2 and 2013 SP1 installations received the update.
- Warn users not to open unexpected or untrusted Office documents.
- Filter or quarantine suspicious document attachments at email and web gateways.
- Check systems that handled untrusted documents for signs of compromise.
The CVE record names no fixed version. This does not mean no fix exists. Follow CISA's required action to apply updates per vendor instructions, and use the Microsoft advisory to identify the correct update for each Office version. Until updates are confirmed, limit the opening of untrusted documents.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-787 Out-of-bounds Write
Questions about CVE-2015-1642
- Is CVE-2015-1642 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-03, with a US federal due date of 2022-03-24. Whether it is used in ransomware campaigns is unknown.
- Can it be exploited without user action?
- No. A user must open a crafted document. CISA rates it as not automatable, but a successful attack gives the attacker total control of the affected component.
- Which Office versions are affected?
- The description names Microsoft Office 2007 SP3, 2010 SP2 and 2013 SP1. The CVE record lists no structured version data, so check the Microsoft advisory for details.
Written with AI from the data on this page and checked against it automatically.
References
Vendor
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.