Menu

Star on GitHub · 3.2k

CVE-2016-7267

5.5 · MEDIUM

Microsoft Excel 2010 SP2, 2013 SP1, 2013 RT SP1, and 2016 misparses file formats, which makes it easier for remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office…

Published Dec 20, 2016CWE-20EPSS 19.41%

Overview

CVE-2016-7267 is a medium-severity vulnerability. It was published on December 20, 2016 and has a CVSS 3.0 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

Microsoft Excel 2010 SP2, 2013 SP1, 2013 RT SP1, and 2016 misparses file formats, which makes it easier for remote attackers to execute arbitrary code via a crafted document, aka "Microsoft Office Security Feature Bypass Vulnerability."

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. 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.

Frequently asked questions

What is CVE-2016-7267?

CVE-2016-7267 is a medium-severity vulnerability. It was published on December 20, 2016 and has a CVSS 3.0 base score of 5.5 (MEDIUM).

How severe is CVE-2016-7267?

This vulnerability has a CVSS 3.0 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2016-7267?

Check the references section for vendor advisories, patches, and mitigation guidance. 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-2016-7267?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-7267 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2016

View all