CVE-2015-1770: Microsoft Office Uninitialized Memory Use
Microsoft Office · listed in the CISA catalog of actively exploited vulnerabilities since 2022-03-28.
- CVSS v3.1 (CISA ADP)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 35%
- higher than 98.4% of all CVEs
- Added to CISA KEV
- 2022-03-28
- US federal due date 2022-04-18
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2015-1770 explained
CVE-2015-1770 is an uninitialized memory use flaw (CWE-824: Access of Uninitialized Pointer) in Microsoft Office 2013 SP1 and 2013 RT SP1. A crafted Office document can let a remote attacker execute arbitrary code. CISA lists it as known to be exploited, so unpatched systems face real risk.
Impact
An attacker who gets a user to open a crafted Office document can execute arbitrary code. No privileges are needed, but user interaction is required. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so each attack needs manual steps. Confidentiality, integrity and availability impacts are all high. Attackers are known to exploit this vulnerability. Ransomware use is unknown.
Who is affected
The description names Microsoft Office 2013 SP1 and Microsoft Office 2013 RT SP1. The CVE record's version data lists no affected versions for Microsoft Office and names no fixed version. This does not mean no fix exists. Check the Microsoft vendor 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 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."
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-04-18 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for Office 2013 SP1 and 2013 RT SP1 as described in the vendor advisory.
- Follow CISA's required action: apply updates per vendor instructions.
- Warn users not to open unexpected Office documents, especially from unknown senders.
- Filter or scan incoming Office attachments at mail and web gateways.
- Check systems that ran unpatched Office 2013 for signs of compromise.
The CVE record names no fixed version. Use the Microsoft vendor advisory to identify the correct updates for Office 2013 SP1 and 2013 RT SP1, and follow CISA's required action to apply updates per vendor instructions. Until updated, limit the opening of untrusted Office documents and filter risky attachments.
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-824 Access of Uninitialized Pointer
Questions about CVE-2015-1770
- Is CVE-2015-1770 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-28, with a US federal due date of 2022-04-18. Whether it is used in ransomware campaigns is unknown.
- Which Office versions are affected?
- The description names Microsoft Office 2013 SP1 and 2013 RT SP1. The CVE record itself lists no affected versions, so check the Microsoft advisory for details.
- Can it be exploited without user action?
- No. A user must open a crafted Office document. No privileges are required for the attacker.
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.