External risk intelligence

Microsoft Visio DLL Side Loading Vulnerability

CVE advisoryKnown Exploit

CVE-2016-3235

Certain Microsoft Visio versions are affected by a library loading vulnerability, allowing local users to gain privileges via a crafted application. This presents a risk of unauthorized access and control over affected systems and data.

1Halo Surface Signal

Microsoft Visio

2007201020132016

External exposure likelihood

Halo Surface Signal score for CVE-2016-3235

This vulnerability involves DLL side loading within local desktop productivity applications (Microsoft Visio and Visio Viewer). It requires a user to open a crafted file locally, meaning it is not reachable via network-based attacks or public internet exposure.

Horizon Alert

Summary of the vulnerability and why it matters

Certain versions of Microsoft Visio and Visio Viewer contain a flaw in how they handle library loading. This weakness allows local users to execute a crafted application that can gain elevated privileges. The primary impact could be unauthorized access and control over affected systems.

  • Visio and Visio Viewer
  • Improper library loading
  • Unauthorized system access

Attack Path

How an attacker could exploit the issue

This vulnerability allows local users to gain privileges by exploiting how Microsoft Visio and Visio Viewer handle library loading. An attacker can leverage a specially crafted application to achieve this. The process involves an attacker tricking a user into running a malicious application that loads a vulnerable library. This can result in unauthorized access and control over the affected system.

  • Local execution on a Visio system
  • Attacker crafts malicious application
  • Triggering library load grants control

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow local users to gain elevated privileges by tricking an organization's employees into opening a specially crafted application. If exploited, it could lead to unauthorized access and modification of sensitive data, impacting business operations and data integrity. Given its inclusion in the Known Exploited Vulnerabilities catalog, organizations should treat this as a significant risk.

  • Attackers with moderate skill.
  • Requires user interaction and local access.
  • High business risk, treat as urgent.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Microsoft Visio and Visio Viewer products. Attackers can exploit this by tricking a user into opening a specially crafted file, potentially leading to unauthorized code execution. This presents a risk to the confidentiality, integrity, and availability of affected systems and data.

  • Identify affected Visio assets.
  • Restrict file access and user privileges.
  • Apply vendor updates and validate.
  • Monitor for related activity.

Frequently asked questions

What is Microsoft Visio and what is it used for?

Microsoft Visio is a diagramming application used for creating flowcharts, organizational charts, network diagrams, and other visual representations of complex information. Visio Viewer allows users to view Visio files without needing the full Visio application.

How does CVE-2016-3235 allow privilege escalation?

CVE-2016-3235 is a DLL side-loading vulnerability. This means that Microsoft Visio and Visio Viewer improperly handle loading dynamic link libraries (DLLs). An attacker can exploit this by providing a specially crafted application that tricks the software into loading a malicious DLL, which can then allow the attacker to gain higher privileges on the system.

What are the preconditions for an attacker to exploit CVE-2016-3235?

An attacker must have local access to a machine running an affected version of Microsoft Visio or Visio Viewer. They also need to trick a user into running a crafted application. The vulnerability is not triggered if a user simply opens a legitimate Visio file that has not been maliciously crafted.

Who should be concerned about this vulnerability?

Organizations with internal networks that include systems running vulnerable versions of Microsoft Visio or Visio Viewer should be concerned. Because the attack vector is local, it is not directly exposed to the public internet, but if an attacker gains initial access to an internal system, they could exploit this vulnerability to escalate privileges.

What is the first step to respond to this threat?

The first practical step is to identify all instances of affected Microsoft Visio and Visio Viewer products within your environment. Once identified, applying the vendor-supplied updates is crucial to remediate the vulnerability.

References