MediumGHSA-5633-f33j-c6f7CVE-2018-8416

Tampering vulnerability in .NET Core

Published 13 May 2022 · Updated 5 Dec 2024

Is your project on an affected Microsoft.NETCore.App?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=2.1.0 <2.1.7
Fixed in
2.1.7
Update to the fixed version for your release line, for example:dotnet add package Microsoft.NETCore.App --version 2.1.7

Details

A tampering vulnerability exists when .NET Core improperly handles specially crafted files, aka ".NET Core Tampering Vulnerability." This affects .NET Core 2.1.

Is GHSA-5633-f33j-c6f7 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Microsoft.NETCore.App, and gives you the command that fixes it.

More advisories for Microsoft.NETCore.App

  • MediumCVE-2021-34485.NET Core Information Disclosure Vulnerability · 20 Oct 2022
  • MediumCVE-2021-1721Denial of service in .NET core · 24 May 2022
  • HighCVE-2020-1147.NET Framework, SharePoint Server, and Visual Studio Remote Code Execution Vulnerability · 24 May 2022
  • HighCVE-2020-1108.NET Core & .NET Framework Denial of Service Vulnerability · 24 May 2022
  • HighCVE-2017-8585Improper Input Validation in Microsoft.NETCore.App · 17 May 2022
  • HighCVE-2019-0564Denial of service in ASP.NET Core · 14 May 2022
All 10 advisories for Microsoft.NETCore.App

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.