CVE-2017-8630
Last modified
CVE-2017-8630 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 20.26% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Microsoft | Office | 2016 |
References
- http://www.securityfocus.com/bid/100732Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039315Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8630Patch, Vendor Advisory
- http://www.securityfocus.com/bid/100732Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039315Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8630Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-8630?
How severe is CVE-2017-8630?
How do I fix CVE-2017-8630?
Are you affected by CVE-2017-8630?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
