dbcve.org
.net FrameworkApplication · Microsoft

CVE-2016-3209

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
High EPSS No privileges

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
Graphics Device Interface (aka GDI or GDI+) 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; Live Meeting 2007 Console; .NET Framework 3.0 SP2, 3.5, 3.5.1, 4.5.2, and 4.6; and Silverlight 5 allows remote attackers to bypass the ASLR protection mechanism via unspecified vectors, aka "True Type Font Parsing Information Disclosure 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

This vulnerability in the Graphics Device Interface (GDI/GDI+) allows remote attackers to bypass ASLR (Address Space Layout Randomization) protection through unspecified vectors related to True Type Font parsing, leading to information disclosure.

MitigationApply Microsoft security updates that address this vulnerability by patching the affected GDI/GDI+ components and True Type Font parsing code across all affected Windows versions, Office products, .NET Framework installations, and Silverlight.

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
.net FrameworkApplication
Affected:= 3.0= 3.5= 3.5.1= 4.5.2= 4.6
Live MeetingApplication
Affected:= 2007
LyncApplication
Affected:= 2010= 2013
OfficeApplication
Affected:= 2007= 2010
SilverlightApplication
Affected:= 5.0
Skype For BusinessApplication
Affected:= 2016
Word ViewerApplication
Affected:all versions
Windows 10Operating system
Affected:all versions= 1511= 1607

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the Windows version
    Affected if Running Windows 10 (any build), Windows 10 version 1511, or Windows 10 version 1607
  2. Check .NET Framework version
    Check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v\Version or run 'Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' | Select-Object Version' in PowerShell
    Affected if Version equals 3.0, 3.5, 3.5.1, 4.5.2, or 4.6
  3. Verify Microsoft Office version
    Run 'winword /?' or check registry HKEY_CLASSES_ROOT\Word.Application\CurVer to determine Office version
    Affected if Office 2007 or Office 2010 is installed
  4. Check Silverlight version
    Visit 'about:silverlight' in a browser or check C:\Program Files\Microsoft Silverlight\version.txt
    Affected if Silverlight version 5.0 is installed
  5. Confirm Lync or Skype for Business version
    Check Add/Remove Programs or run 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' in PowerShell for Lync/Skype for Business entries
    Affected if Lync 2010, Lync 2013, or Skype for Business 2016 is installed

The system is likely affected if any of the identified installed versions match the affected versions listed in the CVE and the corresponding Microsoft security updates have not been applied.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates that address this vulnerability by patching the affected GDI/GDI+ components and True Type Font parsing code across all affected Windows versions, Office products, .NET Framework installations, and Silverlight.

Fix this in .net Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-3209 — 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-3209 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