CVE-2017-11770: Improper Certificate Validation

CVE-2017-11770 · Severity: low · CVSS 3 · Published 2022-04-12

Improper Certificate Validation

Technologies: Microsoft.NETCore.App (NuGet). Vendors: NuGet.

Quick answers

Is CVE-2017-11770 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2017-11770 being exploited in the wild.
How severe is CVE-2017-11770?
Low severity, with a CVSS score of 3, published 12 April 2022.
Which products and versions are affected?
Microsoft.NETCore.App (NuGet) ECOSYSTEM:introduced=1.0.0,fixed=2.0.3; System.Security.Cryptography.X509Certificates (NuGet) ECOSYSTEM:introduced=4.0.0,fixed=4.1.2.
Is there a fix for CVE-2017-11770?
Yes. Microsoft.NETCore.App (NuGet): upgrade to 2.0.3 or later; System.Security.Cryptography.X509Certificates (NuGet): upgrade to 4.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2017-11770?
Check whether you run Microsoft.NETCore.App (NuGet) or System.Security.Cryptography.X509Certificates (NuGet) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Microsoft.NETCore.App (NuGet): upgrade to 2.0.3 or later
    dotnet add package Microsoft.NETCore.App --version 2.0.3
  • System.Security.Cryptography.X509Certificates (NuGet): upgrade to 4.1.2 or later
    dotnet add package System.Security.Cryptography.X509Certificates --version 4.1.2

Affected products

  • Microsoft.NETCore.App (NuGet) ECOSYSTEM:introduced=1.0.0,fixed=2.0.3
  • System.Security.Cryptography.X509Certificates (NuGet) ECOSYSTEM:introduced=4.0.0,fixed=4.1.2

Identifiers

  • CVE-2017-11770
  • GHSA-7mfr-774f-w5r9

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.