LiveActive security incident?Get immediate response
CVE Record

CVE-2017-8630: Microsoft Office 2016 allows a remote code execution vulnerability when it fails to properly handle objects...

Microsoft Office 2016 allows a remote code execution vulnerability when it fails to properly handle objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8631, CVE-2017-8632, and CVE-2017-8744.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2017-8630 is a Microsoft Office 2016 memory corruption issue that could allow remote code execution. In business terms, an affected Office installation may let attacker-controlled Office content run code if the vulnerable handling path is reached. The source bundle does not provide CVSS, exploit prerequisites, or a confirmed exploitation claim. Exposure is limited by the provided evidence to Microsoft Office 2016 installations. Risk is most relevant on endpoints where users open or preview externally supplied Office content. The bundle does not identify other Office versions or platforms as affected. Prioritize remediation if Office 2016 is still present, especially on user workstations exposed to external documents. The lack of CVSS and exploit details lowers certainty, but the potential business impact of Office remote code execution is significant. Mitigation focus: Review the Microsoft MSRC advisory for CVE-2017-8630.; Apply applicable Microsoft Office 2016 security updates from Microsoft guidance.; Prioritize endpoints that handle external documents or email attachments..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-8630 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Microsoft CorporationMicrosoft OfficeMicrosoft Office 2016Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.