dbcve.org
.net FrameworkApplication · Microsoft

CVE-2014-1806

HIGH · 10.0 CVSS v2.0 Published 2014-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The .NET Remoting implementation in Microsoft .NET Framework 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly restrict memory access, which allows remote attackers to execute arbitrary code via vectors involving malformed objects, aka "TypeFilterLevel Vulnerability."

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

The .NET Remoting implementation in multiple Microsoft .NET Framework versions fails to properly restrict memory access during deserialization of objects. Attackers can send malformed objects that, when deserialized by a vulnerable server, allow arbitrary code execution due to insufficient TypeFilterLevel filtering.

MitigationApply Microsoft security updates for CVE-2014-1806 to all affected .NET Framework installations. If immediate patching is not feasible, disable or restrict .NET Remoting services and ensure proper network isolation.

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
.net FrameworkApplication
Affected:= 1.1= 2.0= 3.5= 3.5.1= 4.0= 4.5= 4.5.1

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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

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

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. Identify installed .NET Framework version
    Check the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v\Full\Version or use 'Get-ItemProperty' PowerShell cmdlet against HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v\Full
    Affected if The installed version matches 1.1, 2.0, 3.5, 3.5.1, 4.0, 4.5, or 4.5.1
  2. Determine if .NET Remoting server is in use
    Search application config files (app.config, machine.config) for '<system.runtime.remoting>' sections, and review running services or applications that expose .NET Remoting endpoints via TcpServerChannel or HttpServerChannel
    Affected if .NET Remoting server channels are configured and exposed to the network or untrusted clients
  3. Inspect TypeFilterLevel configuration
    Review remoting channel configuration in config files or code for 'typeFilterLevel' attribute on <channel> elements; check if it is explicitly set to 'Full' or if it remains at the default setting
    Affected if TypeFilterLevel is not explicitly set to 'Full' (or is set to 'Low') on a Remoting server that handles deserialization of client-supplied objects

A system is affected if it runs any of the listed .NET Framework versions AND exposes a .NET Remoting server endpoint with TypeFilterLevel not explicitly configured to Full, allowing deserialization of untrusted objects.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for CVE-2014-1806 to all affected .NET Framework installations. If immediate patching is not feasible, disable or restrict .NET Remoting services and ensure proper network isolation.

Recommended fix High confidence

Upgrade to .NET Framework 4.8 (or latest supported version) on Windows Server 2019+ / Windows 10+ for long-term support; migrate away from .NET Remoting to WCF or modern APIs

  1. Identify the exact .NET Framework version installed on each affected system using Registry Editor (HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\vXXXX\Version)
  2. Apply Microsoft Security Bulletin MS14-026 patch: KB2958732 for all affected .NET Framework versions
  3. For .NET Framework 1.1 SP1: Install KB2931476 (Security Update for .NET Framework 1.1 SP1)
  4. For .NET Framework 2.0 SP2: Install KB2932079 (Security Update for .NET Framework 2.0 SP2)
  5. For .NET Framework 3.5: Install KB2931356 (Security Update for .NET Framework 3.5)
  6. For .NET Framework 3.5.1: Install KB2931357 (Security Update for .NET Framework 3.5.1 on Windows 7/Server 2008 R2)
  7. For .NET Framework 4 and 4.5.x: Install KB2958732 (Security Update for .NET Framework 4/4.5/4.5.1)
  8. Restart affected systems after applying patches
Caveat Upgrading from .NET Framework 1.1/2.0 may require code changes if using deprecated APIs; .NET Remoting itself is legacy and migration to WCF/gRPC recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in .net Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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