CVE-2017-8630 Memory corruption in Microsoft Office

High 7.8 Published Updated

Remote attackers can execute arbitrary code by exploiting a memory corruption flaw in Microsoft Office 2016.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2017-8630?

CVE-2017-8630 is a high-severity memory corruption vulnerability in Microsoft Office, published on 13 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

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.

Weakness: CWE-119

Which versions are affected by CVE-2017-8630?

It affects 1 product.

Products include Microsoft Office.

How do I fix CVE-2017-8630?

No fix has been published for CVE-2017-8630 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2017-8630 being exploited?

There is no known exploitation of CVE-2017-8630 in the wild and no public exploit code.

All Microsoft Office vulnerabilities

Sources

Also known as GHSA-4r2h-p7qv-cxcx.

Is CVE-2017-8630 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free