CVE-2016-3304

This flaw is in Windows’ handling of fonts. Attackers can hide malicious content inside something you might open (like a document or other embedded content), and when the system processes that font it can end up running attacker code. Think of it like a “looking-glass” file format: the file looks normal, but the font payload is the part that does the damage.

This matters if your business uses affected Microsoft Windows versions (like Windows Vista SP2, Windows Server 2008 SP2/R2 SP1, Windows 7 SP1) and/or affected Office and communication apps (Office 2007 SP3, Office 2010 SP2, Word Viewer, Skype for Business 2016, Lync 2013 SP1, Live Meeting).

Because the weakness requires user interaction (opening/processing crafted content), it’s mainly a risk if an attacker can send you a crafted file or content that your staff opens on an unpatched machine.

This is AMBER because there is a public exploit available and the problem lets attackers run code on unpatched machines through crafted embedded fonts. Even without a confirmed “actively exploited in the wild” listing, the availability of weaponized tooling means you should prioritize patching now rather than later.