CVE-2017-8725
UnknownEPSS 19.59%
Last modified
CVE-2017-8725 is a vulnerability of currently unknown severity. A remote code execution vulnerability exists in Microsoft Publisher 2007 Service Pack 3 and Microsoft Publisher 2010 Service Pack 2 when they fail to properly handle objects in memory, aka "Microsoft Office Publisher Remote Code Execution".. EPSS estimates a 19.59% chance of exploitation in the next 30 days.
Description
A remote code execution vulnerability exists in Microsoft Publisher 2007 Service Pack 3 and Microsoft Publisher 2010 Service Pack 2 when they fail to properly handle objects in memory, aka "Microsoft Office Publisher Remote Code Execution".
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Microsoft | Publisher | 2007 | Sp3 |
| Microsoft | Publisher | 2010 | Sp2 |
References
- http://www.securityfocus.com/bid/100758Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039322Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8725Patch, Vendor Advisory
- http://www.securityfocus.com/bid/100758Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1039322Third Party Advisory, VDB Entry
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8725Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-8725?
A remote code execution vulnerability exists in Microsoft Publisher 2007 Service Pack 3 and Microsoft Publisher 2010 Service Pack 2 when they fail to properly handle objects in memory, aka "Microsoft Office Publisher Remote Code Execution".
How severe is CVE-2017-8725?
Severity scoring for CVE-2017-8725 is pending analysis. The EPSS model estimates a 19.59% probability of exploitation in the next 30 days.
How do I fix CVE-2017-8725?
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-8717The Microsoft JET Database Engine in Windows Server 2008 SP2…
- CVE-2017-8718The Microsoft JET Database Engine in Windows Server 2008 SP2…
- CVE-2017-8719The Windows kernel component on Microsoft Windows Server 200…
- CVE-2017-8720The Microsoft Windows graphics component on Microsoft Window…
- CVE-2017-8723Microsoft Edge in Microsoft Windows 10 Gold, 1511, 1607, 170…
- CVE-2017-8724Microsoft Edge in Microsoft Windows 10 Version 1703 allows a…
- CVE-2017-8726Microsoft Edge in Microsoft Windows 10 Gold, 1511, 1607, 170…
- CVE-2017-8727Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1,…
- CVE-2017-8728Microsoft Windows PDF Library in Microsoft Windows 8.1 and W…
- CVE-2017-8729Microsoft Edge in Microsoft Windows 10 1703 allows an attack…
- CVE-2017-8731Microsoft Edge in Microsoft Windows 10 1607 and Windows Serv…
- CVE-2017-8733Internet Explorer in Microsoft Windows 7 SP1, Windows Server…
Are you affected by CVE-2017-8725?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST