CVE-2015-1770

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."

CVSS: 8.8Highscored by CISA
Exploited in the wild: Yes, in CISA KEV since 28 Mar 2022CISA deadline for US federal agencies: 18 Apr 2022
EPSS: 35.0%chance of exploitation in the next 30 daystop 2% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 10 Jun 2015analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable: At runtime
Attack vector: network
Weakness: CWE-824 Common Weakness
Can a WAF block it?: Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

microsoft:office

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 28 Mar 2022.
CISA due date: 18 Apr 2022, the remediation deadline for US federal agencies
CISA required action: Apply updates per vendor instructions.
Public exploit code: None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC: exploitation active, automatable no, technical impact totalAssessed by CISA 10 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

10 Jun 2015Published
28 Mar 2022Added to CISA KEV (exploited in the wild)2,483 days (about 7 years) later
18 Apr 2022CISA remediation due date (US federal agencies)21 days later
10 Feb 2025CISA SSVC assessment: exploitation active1,030 days (about 3 years) later
21 Oct 2025CVE record last updated253 days (about 8 months) later
12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	RequiredA victim must click, open or otherwise cooperate.	A victim must click, open or otherwise cooperate.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	HighFull outage possible.	Full outage possible.

Common questions

Is CVE-2015-1770 being exploited?

Yes. CVE-2015-1770 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2015-1770?

CVE-2015-1770 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2015-1770?

Yes. A fix has been recorded for CVE-2015-1770. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2015-1770 affect?

CVE-2015-1770 affects microsoft:office. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

4 references in the CVE record, grouped by the tags the record gives them.

Advisories (1)

docs.microsoft.com /en-us/security-updates/securitybulletins/2015/ms15-059

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.