CVE Tools

CVE-2016-0092

Exploitation likely. EPSS gives it a 57% chance of exploitation in the next 30 days. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether any computers run Windows Vista SP2, Windows 7 SP1, Windows 8.1, Windows RT 8.1, Windows 10 Gold or 1511, or the listed Windows Server releases.
  2. Install the security updates recommended in Microsoft Security Bulletin MS16-030; the findings do not provide a single fixed Windows version.
  3. Until updated, block or quarantine unexpected document attachments and files from untrusted sources.
  4. Ask IT to investigate any suspicious file opened on an affected computer.

What it is

From the CVE record

OLE 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, and Windows 10 Gold and 1511 allows remote attackers to execute arbitrary code via a crafted file, aka "Windows OLE Memory Remote Code Execution Vulnerability," a different vulnerability than CVE-2016-0091.

In plain language

Written by AI from the record

This affects older supported-at-the-time Windows releases from Windows Vista SP2 through Windows 10 version 1511; act if any of those systems still open email attachments or shared files.

Windows OLE input-handling flaw (CWE-20) permits arbitrary code execution when a victim opens or processes a crafted OLE file.

If you're affected

  • Full computer takeover
  • Business file theft
  • Ransomware installation
  • Operational disruption
  • Fraudulent email access

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS99th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

57% chance of exploitation activity in the next 30 days, which ranks it in the 99th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

24 events over 3850 days, from the signal feeds we watch.

  1. EPSS band changemoderate → highepss band change
  2. EPSS band changehigh → moderateepss band change
  3. EPSS band changemoderate → highepss band change
  4. EPSS band changehigh → moderateepss band change
  5. EPSS band changemoderate → highepss band change
  6. EPSS band changehigh → moderate

Affected products

Technical detail

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

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Windows 10 1511, not every advisory.