System.ServiceModel.NetTcp vulnerabilities
System.ServiceModel.NetTcp
- Registry
- NuGet
- Latest
- 10.1.0
- License
- MIT
2 known advisories
The latest version, 10.1.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
dotnet add package System.ServiceModel.NetTcp --version 10.1.0Is your project on an affected System.ServiceModel.NetTcp?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for System.ServiceModel.NetTcp
Improper Certificate Validation in Microsoft .NET Framework components
- Affected
- >=4.3.0 <4.3.3 · >=4.4.0 <4.4.4 · >=4.5.0 <4.5.3 · >=4.0.0 <4.1.3
- Fixed in
- 4.1.3, 4.3.3, 4.4.4, 4.5.3
Improper Certificate Validation in Microsoft .NET Framework components
- Affected
- >=4.4.0 <4.4.1 · >=4.3.0 <4.3.1 · >=4.1.0 <4.1.1
- Fixed in
- 4.1.1, 4.3.1, 4.4.1
Is your System.ServiceModel.NetTcp version vulnerable?
- System.ServiceModel.NetTcp 10.1No known advisories in 10.1.0
- System.ServiceModel.NetTcp 10.0No known advisories in 10.0.652802
- System.ServiceModel.NetTcp 8.1No known advisories in 8.1.2
- System.ServiceModel.NetTcp 8.0No known advisories in 8.0.0
- System.ServiceModel.NetTcp 6.2No known advisories in 6.2.0
- System.ServiceModel.NetTcp 6.1No known advisories in 6.1.0
- System.ServiceModel.NetTcp 6.0No known advisories in 6.0.0
Which of your client projects still run an old System.ServiceModel.NetTcp?
NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other NuGet packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.