CVE-2016-7213

UnknownEPSS 19.28%

Last modified

CVE-2016-7213 is a vulnerability of currently unknown severity. Microsoft Excel 2007 SP3, Excel 2010 SP2, Excel 2013 SP1, Excel 2013 RT SP1, Excel 2016, Excel for Mac 2011, Excel 2016 for Mac, and Office Compatibility Pack SP3 allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability.". EPSS estimates a 19.28% chance of exploitation in the next 30 days.

Description

Microsoft Excel 2007 SP3, Excel 2010 SP2, Excel 2013 SP1, Excel 2013 RT SP1, Excel 2016, Excel for Mac 2011, Excel 2016 for Mac, and Office Compatibility Pack SP3 allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."

Metrics

EPSS Probability
19.28%

97.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
MicrosoftExcel2007Sp3
MicrosoftExcel2010Sp2
MicrosoftExcel2013Sp1
MicrosoftExcel2016
MicrosoftExcel For Mac2011
MicrosoftExcel For Mac2016
MicrosoftOffice Compatibility PackAll versionsSp3

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2016-7213?
Microsoft Excel 2007 SP3, Excel 2010 SP2, Excel 2013 SP1, Excel 2013 RT SP1, Excel 2016, Excel for Mac 2011, Excel 2016 for Mac, and Office Compatibility Pack SP3 allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."
How severe is CVE-2016-7213?
Severity scoring for CVE-2016-7213 is pending analysis. The EPSS model estimates a 19.28% probability of exploitation in the next 30 days.
How do I fix CVE-2016-7213?
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.

Are you affected by CVE-2016-7213?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST