dbcve.org
Live MeetingApplication · Microsoft

CVE-2016-7182

CRITICAL · 9.8 CVSS v3.0 Published 2016-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Graphics component in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; Windows 10 Gold, 1511, and 1607; Office 2007 SP3; Office 2010 SP2; Word Viewer; Skype for Business 2016; Lync 2013 SP1; Lync 2010; Lync 2010 Attendee; and Live Meeting 2007 Console allows attackers to execute arbitrary code via a crafted True Type font, aka "True Type Font Parsing Elevation of Privilege Vulnerability."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability exists in the font parsing functionality of the Windows Graphics component and multiple Office products. Attackers can exploit this by tricking users into loading a specially crafted True Type font file, which triggers a buffer overflow allowing arbitrary code execution with elevated privileges.

MitigationApply the Microsoft security updates (MS16-120 or subsequent related patches) to all affected Windows and Office installations. Restrict font loading permissions and scan for suspicious .ttf files as an additional defensive measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Live MeetingApplication
Affected:= 2007
LyncApplication
Affected:= 2010= 2013
OfficeApplication
Affected:= 2007= 2010
Skype For BusinessApplication
Affected:= 2016
Word ViewerApplication
Affected:all versions
Windows 10Operating system
Affected:all versions= 1511= 1607
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the Windows edition and build number
    Affected if Version is Windows 7 (any build), Windows 8.1 (any build), or Windows 10 (any build including 1511 and 1607)
  2. Check installed Microsoft Office or related product version
    Open the application, go to File > Account > About [Product], or check Programs and Features for the exact version number
    Affected if Product is Microsoft Office 2007, Office 2010, Lync 2010, Lync 2013, Skype for Business 2016, Live Meeting 2007, or Word Viewer (any version)
  3. Verify MS16-120 security update is installed
    Run 'wmic qfe list | findstr "KB3197823"' or open Control Panel > Programs > View installed updates and search for KB3197823 (the MS16-120 update for this CVE)
    Affected if The KB3197823 update is NOT installed on the system
  4. Confirm font loading capability is present
    Check if the system allows loading TrueType fonts - this is standard behavior on unhardened systems. No specific command needed; standard user accounts with font installation rights can trigger the vulnerability
    Affected if Standard user or administrative accounts can load .ttf files onto the system (default condition)

The environment is affected if running any of the vulnerable Windows or Office versions listed AND the MS16-120 (KB3197823) security update has not been installed, allowing specially crafted .ttf files to be loaded.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Microsoft security updates (MS16-120 or subsequent related patches) to all affected Windows and Office installations. Restrict font loading permissions and scan for suspicious .ttf files as an additional defensive measure.

Recommended fix High confidence
  1. Check Microsoft Update or Windows Update for available security updates
  2. For Windows systems: Install the relevant security update from Microsoft. For this CVE, look for MS16-120 (Security Update for Microsoft Graphics Component)
  3. For Office products: Install the relevant Office security updates from Microsoft Update catalog
  4. For Lync/Skype for Business: Apply the corresponding security update for the affected version
  5. After applying updates, restart the affected systems to complete the remediation
  6. Verify the updates are installed by checking the installed updates list or using the Get-HotFix PowerShell cmdlet

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Live Meeting Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-7182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-7182 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data