CVE-2017-8725 Memory corruption in Microsoft Office

High 7.8 Published Updated

Remote attackers can execute arbitrary code by exploiting a memory handling flaw in Microsoft Publisher.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2017-8725?

CVE-2017-8725 is a high-severity memory corruption vulnerability in Microsoft Office, published on 13 Sep 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official 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".

Weakness: CWE-119

Which versions are affected by CVE-2017-8725?

It affects 1 product.

Products include Microsoft Publisher.

How do I fix CVE-2017-8725?

No fix has been published for CVE-2017-8725 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2017-8725 being exploited?

There is no known exploitation of CVE-2017-8725 in the wild and no public exploit code.

Sources

Also known as GHSA-wh24-m3cp-5hcg.

Is CVE-2017-8725 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free