CVE Tools
Track your stack

CVE-2014-0257

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

CVSS 2.09.3CriticalEPSS percentile99th70% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
Public exploit: 2 sourcesFixVendor fixNo build named by the sources

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

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 installed Microsoft .NET Framework versions on every Windows computer and server, especially older business applications.
  2. Install the Microsoft security update described in MS14-009; the supplied findings do not identify a single replacement version number.
  3. Until updated, limit use of affected applications and prevent untrusted websites or files from reaching affected systems.
  4. Ask your IT provider to check affected machines for unexpected software, accounts, or network activity after remediation.
Some work to apply
Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly determine whether it is safe to execute a method, which allows remote attackers to execute arbitrary code via (1) a crafted web site or (2) a crafted .NET Framework application that exposes a COM server endpoint, aka "Type Traversal Vulnerability."

In plain language

Written by AI from the record

Microsoft .NET Framework 1.0 SP3, 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4.0, 4.5, and 4.5.1 have a critical flaw; businesses using these older versions should act urgently.

CVE-2014-0257 is a CWE-20 type-traversal vulnerability in Microsoft .NET Framework that can allow remote arbitrary code execution through a crafted website or a .NET application exposing a COM server endpoint.

If you're affected

  • Unauthorized software execution
  • Server takeover risk
  • Business service disruption
  • Sensitive data exposure

Exploitation

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

EPSS99th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

2 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

70% 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

A public exploit existed 53 days before the patch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Public exploit / PoCsource: packetstorm
  4. Publishedweakness classified, att&ck mapped

Affected products

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

Technical detail

CVSS 2.0 vector

Open in the CVSS calculator

AV:N/AC:M/Au:N/C:C/I:C/A:C

Scored 9.3 by NVD.

How it is reached

  • Access Vector NetworkExploitable remotely over the network
  • Access Complexity MediumSome conditions must be met
  • Authentication NoneNo authentication required

Impact if exploited

  • Confidentiality CompleteAll information is disclosed
  • Integrity CompleteAll data can be modified
  • Availability CompleteTotal shutdown of the affected resource

Weaknesses

ATT&CK techniques

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

Sources

References in the record

And 6 more references. See all after sign-in

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 Microsoft Corp, not every advisory. This one: public exploit.