dbcve.org
Live MeetingApplication · Microsoft

CVE-2016-3262

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
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; and Live Meeting 2007 Console allows remote attackers to bypass the ASLR protection mechanism via unspecified vectors, aka "GDI+ Information Disclosure Vulnerability," a different vulnerability than CVE-2016-3263.

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

GDI+ (Graphics Device Interface) contains an information disclosure vulnerability that allows remote attackers to bypass ASLR (Address Space Layout Randomization) protection. The vulnerability leaks memory addresses that can be used to defeat ASLR randomization, making other memory corruption vulnerabilities easier to exploit.

MitigationApply Microsoft security updates for affected products. Deploy EMET (Enhanced Mitigation Experience Toolkit) or enable Windows Defender Exploit Guard ASLR settings as compensating controls until patches are applied.

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
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. Check Windows version to see if it is affected
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the Windows version. For Windows 10, also check the build number via 'winver' (look for version 1511 or 1607 specifically, or any version for 'all versions' claim).
    Affected if Windows 7 (any version), Windows 8.1 (any version), Windows 10 (any version including 1511 and 1607), or Windows Server versions that include GDI+.
  2. Check Microsoft Office version
    Open any Office application, go to File > Account > About [App] or run 'winword /?' or 'excel /?' from command line to see the version. Check for versions 2007 or 2010.
    Affected if Microsoft Office 2007 or Microsoft Office 2010 is installed.
  3. Check Microsoft Lync or Skype for Business version
    Open Lync 2010/2013 or Skype for Business, click on the user picture or go to File > Help > About. Alternatively, check Add/Remove Programs or the program's executable properties.
    Affected if Microsoft Lync 2010, Lync 2013, or Skype for Business 2016 is installed.
  4. Check for Microsoft Live Meeting 2007
    Check Add/Remove Programs or look for 'Microsoft Office Live Meeting 2007' in installed programs. Check the program version via its Help > About menu if accessible.
    Affected if Microsoft Live Meeting 2007 is installed.
  5. Check for Microsoft Word Viewer
    Check Add/Remove Programs for 'Microsoft Word Viewer' or look for the WordView.exe executable. This product has all versions affected.
    Affected if Microsoft Word Viewer of any version is installed.
  6. Verify GDI+ component presence
    Locate gdiplus.dll on the system - typically in C:\Windows\System32\ or within Office program folders. Check its version by right-clicking the file, selecting Properties, and viewing the Details tab. This DLL is the vulnerable component.
    Affected if The gdiplus.dll file exists on the system (which is true for all Windows installations with affected products).

You are affected if any of the following are true: Windows 7, Windows 8.1, or any version of Windows 10 is running; OR Microsoft Office 2007 or 2010 is installed; OR Lync 2010/2013 or Skype for Business 2016 is installed; OR Microsoft Live Meeting 2007 is present; OR Microsoft Word Viewer of any version is installed.

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 for affected products. Deploy EMET (Enhanced Mitigation Experience Toolkit) or enable Windows Defender Exploit Guard ASLR settings as compensating controls until patches are applied.

Fix this in Live Meeting Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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