CVE-2017-8630

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.

Category

7.8
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 21.88% Top 5%
Vendor Advisory microsoft.com
Affected: Microsoft Corporation Microsoft Office
Published at:
Updated at:

References

Link Tags
https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8630 patch vendor advisory
http://www.securityfocus.com/bid/100732 vdb entry third party advisory
http://www.securitytracker.com/id/1039315 vdb entry third party advisory

Frequently Asked Questions

What is the severity of CVE-2017-8630?
CVE-2017-8630 has been scored as a high severity vulnerability.
How to fix CVE-2017-8630?
To fix CVE-2017-8630, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-8630 being actively exploited in the wild?
It is possible that CVE-2017-8630 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~22% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-8630?
CVE-2017-8630 affects Microsoft Corporation Microsoft Office.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.