CVE Tools

CVE-2014-8985

Exploitation likely. EPSS gives it a 9.8% 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.

  • Microsoft Corp Internet ExplorerAffected: 11Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check whether any business PCs still use Microsoft Internet Explorer 11 as a web browser.
  2. Verify those PCs are updated with the fix described in MS14-051 (Microsoft Internet Explorer memory corruption vulnerability).
  3. If IE11 is installed but not needed, remove it or switch users to a supported browser (and restrict IE11 usage).
  4. If you cannot patch right away, block access to untrusted websites and email links in IE11 until updates are installed, then confirm the update is applied.

What it is

From the CVE record

Microsoft Internet Explorer 11 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Internet Explorer Memory Corruption Vulnerability," a different vulnerability than CVE-2014-2810, CVE-2014-2811, CVE-2014-2822, CVE-2014-2823, CVE-2014-4057, and CVE-2014-4145.

In plain language

Written by AI from the record

CVE-2014-8985 is a Microsoft Internet Explorer 11 security flaw where a specially made website could crash the browser or, in some cases, run attacker code—typical small businesses should worry if they still use IE11 and haven’t installed the matching Microsoft update (MS14-051).

In Microsoft Internet Explorer 11, CVE-2014-8985 is a memory-corruption flaw (CWE-119) reachable through a crafted website that can lead to arbitrary code execution or denial of service; a Microsoft remediation is documented in MS14-051, and there’s no CISA KEV listing and no public exploit code on record.

If you're affected

  • Browser crash and lost work
  • Possibility of attacker code execution
  • Account/session compromise risk
  • Operational disruption from malware

Exploitation

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

EPSS96th
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

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

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

Lifecycle

25 events over 3148 days, from the signal feeds we watch.

  1. EPSS band changemoderate → lowepss band change
  2. EPSS band changelow → moderateepss band change
  3. EPSS band changemoderate → lowepss band change
  4. EPSS band changelow → moderateepss band change
  5. EPSS band changemoderate → lowepss band change
  6. EPSS band changelow → moderate

Affected products

And 2 more affected products. See all after sign-in

Technical detail

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

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • 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 Internet Explorer, not every advisory.