CVE-2015-6172
Overview
CVE-2015-6172 is a known-severity vulnerability affecting microsoft office. It was published on December 9, 2015.
Technical Description
Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, Word 2016, Word 2013 RT SP1, and Office Compatibility Pack SP3 allow remote attackers to execute arbitrary code via a crafted email message processed by Outlook, aka "Microsoft Office RCE Vulnerability."
Remediation
Check the references section for vendor advisories and patches from microsoft. Update office to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|
Frequently Asked Questions
What is CVE-2015-6172?
CVE-2015-6172 is a known-severity vulnerability affecting microsoft office. It was published on December 9, 2015.
How severe is CVE-2015-6172?
CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.
How do I fix or remediate CVE-2015-6172?
Check the references section for vendor advisories and patches from microsoft. Update office to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2015-6172?
CyberStrike's AI-powered security agents can automatically detect CVE-2015-6172 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.