CVE-2017-8501
UnknownEPSS 22.50%
Last modified
CVE-2017-8501 is a vulnerability of currently unknown severity. Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8502.. EPSS estimates a 22.50% chance of exploitation in the next 30 days.
Description
Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8502.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Microsoft | Excel | 2007 | Sp3 |
| Microsoft | Excel | 2010 | Sp2 |
| Microsoft | Excel | 2013 | Sp1 |
| Microsoft | Excel | 2016 | — |
| Microsoft | Excel Viewer | 2007 | Sp3 |
| Microsoft | Office | 2011 | — |
| Microsoft | Office | 2016 | — |
| Microsoft | Office Compatibility Pack | All versions | Sp3 |
| Microsoft | Office Online Server | 2016 | — |
| Microsoft | Sharepoint Server | 2010 | Sp2 |
| Microsoft | Sharepoint Server | 2013 | — |
References
- http://www.securityfocus.com/bid/99441Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038851Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2017-8501Patch, Vendor Advisory
- http://www.securityfocus.com/bid/99441Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038851Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/CVE-2017-8501Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-8501?
Microsoft Office allows a remote code execution vulnerability due to the way that it handles objects in memory, aka "Microsoft Office Memory Corruption Vulnerability". This CVE ID is unique from CVE-2017-8502.
How severe is CVE-2017-8501?
Severity scoring for CVE-2017-8501 is pending analysis. The EPSS model estimates a 22.50% probability of exploitation in the next 30 days.
How do I fix CVE-2017-8501?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-8494Microsoft Windows 10 Gold, 1511, 1607, and 1703, and Windows…
- CVE-2017-8495Microsoft Windows 7 SP1, Windows Server 2008 SP2 and R2 SP1,…
- CVE-2017-8496Microsoft Edge in Windows 10 1607 and Windows Server 2016 al…
- CVE-2017-8497Microsoft Edge in Windows 10 1607 and Windows Server 2016 al…
- CVE-2017-8498Microsoft Edge in Windows 10 1607 and 1703, and Windows Serv…
- CVE-2017-8499Microsoft Edge in Windows 10 1703 allows an attacker to exec…
- CVE-2017-8502Microsoft Office allows a remote code execution vulnerabilit…
- CVE-2017-8503Microsoft Edge in Microsoft Windows 10 1511, 1607, 1703, and…
- CVE-2017-8504Microsoft Edge in Windows 10 1607 and 1703, and Windows Serv…
- CVE-2017-8506A remote code execution vulnerability exists in Microsoft Of…
- CVE-2017-8507A remote code execution vulnerability exists in the way Micr…
- CVE-2017-8508A security feature bypass vulnerability exists in Microsoft …
Are you affected by CVE-2017-8501?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST