ghsa-q7cg-43mg-qp69
Vulnerability from github
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0, .NET Core 3.1 and .NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
An information disclosure vulnerability exists in .NET 5.0, .NET Core 3.1 and .NET Core 2.1 where a JWT token is logged if it cannot be parsed.
Patches
-
If you're using .NET 5.0, you should download and install Runtime 5.0.9 or SDK 5.0.206 (for Visual Studio 2019 v16.8) or SDK 5.0.303 (for Visual Studio 2019 V16.10) from https://dotnet.microsoft.com/download/dotnet-core/5.0.
-
If you're using .NET Core 3.1, you should download and install Runtime 3.1.18 or SDK 3.1.118 (for Visual Studio 2019 v16.4) or 3.1.412 (for Visual Studio 2019 v16.7 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1.
-
If you're using .NET Core 2.1, you should download and install Runtime 2.1.29 or SDK 2.1.525 (for Visual Studio 2019 v15.9) or 2.1.817 from https://dotnet.microsoft.com/download/dotnet-core/2.1.
-
If your application is using .NET Core 2.1 running on .NET Framework see the Updating .NET Core 2.1 on .NET Framework section below.
Updating .NET Core 2.1 on .NET Framework
If you are running .NET Core 2.1 on .NET Framework you need to check your projects for dependencies and update them accordingly.
Direct dependencies
Direct dependencies are discoverable by examining your csproj
file. They can be fixed by editing the project file or using NuGet to update the dependency.
Transitive dependencies
Transitive dependencies occur when you add a package to your project that in turn relies on another package. For example, if Contoso publishes a package Contoso.Utility
which, in turn, depends on Contoso.Internals
and you add the Contoso.Utility
package to your project now your project has a direct dependency on Contoso.Utility
and, because Contoso.Utility
depends 'Contoso.Internals', your application gains a transitive dependency on the Contoso.Internals
package.
Transitive dependencies are reviewable in two ways:
- In the Visual Studio Solution Explorer window, which supports searching.
- By examining the
project.assets.json
file contained in the obj directory of your project forcsproj
based projects
The project.assets.json
files are the authoritative list of all packages used by your project, containing both direct and transitive dependencies.
There are two ways to view transitive dependencies. You can either use Visual Studio’s Solution Explorer, or you can review the project.assets.json
file).
Using Visual Studio Solution Explorer
To use Solution Explorer, open the project in Visual Studio, and then press Ctrl+; to activate the search in Solution Explorer. Search for the vulnerable package and make a note of the version numbers of any results you find.
For example, search for Microsoft.AspNetCore.Authentication.JwtBearer
and update the package to the latest version
Manually reviewing project.assets.json
Open the project.assets.json file from your project’s obj directory in your editor. We suggest you use an editor that understands JSON and allows you to collapse and expand nodes to review this file. Visual Studio and Visual Studio Code provide JSON friendly editing.
Search the project.assets.json file for the vulnerable package, using the format packagename/
for each of the package names from the preceding table. If you find the assembly name in your search:
- Examine the line on which they are found, the version number is after the
/
. - Compare to the vulnerable versions table.
For example, a search result that shows Microsoft.AspNetCore.Authentication.JwtBearer/2.1.0
is a reference to version 2.1.1 of Microsoft.AspNetCore.Authentication.JwtBearer
.
If your project.assets.json file includes references to the vulnerable package, then you need to fix the transitive dependencies.
If you have not found any reference to any vulnerable packages, this means either
- None of your direct dependencies depend on any vulnerable packages, or
- You have already fixed the problem by updating the direct dependencies.
Other Details
- Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/195
- An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/35246
- MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-34532
{ "affected": [ { "package": { "ecosystem": "NuGet", "name": "Microsoft.AspNetCore.Authentication.JwtBearer" }, "ranges": [ { "events": [ { "introduced": "2.1.0" }, { "fixed": "2.1.29" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "NuGet", "name": "Microsoft.AspNetCore.Authentication.JwtBearer" }, "ranges": [ { "events": [ { "introduced": "3.0.0" }, { "fixed": "3.1.18" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "NuGet", "name": "Microsoft.AspNetCore.Authentication.JwtBearer" }, "ranges": [ { "events": [ { "introduced": "5.0.0" }, { "fixed": "5.0.9" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2021-34532" ], "database_specific": { "cwe_ids": [], "github_reviewed": true, "github_reviewed_at": "2021-08-24T18:52:16Z", "nvd_published_at": "2021-08-12T18:15:00Z", "severity": "MODERATE" }, "details": "Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 5.0, .NET Core 3.1 and .NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.\n\nAn information disclosure vulnerability exists in .NET 5.0, .NET Core 3.1 and .NET Core 2.1 where a JWT token is logged if it cannot be parsed.\n\n### Patches\n\n* If you\u0027re using .NET 5.0, you should download and install Runtime 5.0.9 or SDK 5.0.206 (for Visual Studio 2019 v16.8) or SDK 5.0.303 (for Visual Studio 2019 V16.10) from https://dotnet.microsoft.com/download/dotnet-core/5.0.\n\n* If you\u0027re using .NET Core 3.1, you should download and install Runtime 3.1.18 or SDK 3.1.118 (for Visual Studio 2019 v16.4) or 3.1.412 (for Visual Studio 2019 v16.7 or later) from https://dotnet.microsoft.com/download/dotnet-core/3.1.\n\n* If you\u0027re using .NET Core 2.1, you should download and install Runtime 2.1.29 or SDK 2.1.525 (for Visual Studio 2019 v15.9) or 2.1.817 from https://dotnet.microsoft.com/download/dotnet-core/2.1.\n\n* If your application is using .NET Core 2.1 running on .NET Framework see the [Updating .NET Core 2.1 on .NET Framework](#updating-2.1) section below.\n\n### \u003ca name=\"updating-2.1\"\u003e\u003c/a\u003e Updating .NET Core 2.1 on .NET Framework\nIf you are running .NET Core 2.1 on .NET Framework you need to check your projects for dependencies and update them accordingly.\n\n#### Direct dependencies\n\nDirect dependencies are discoverable by examining your `csproj` file. They can be fixed by [editing the project file](#fixing-direct-dependencies) or using NuGet to update the dependency.\n\n#### Transitive dependencies\n\nTransitive dependencies occur when you add a package to your project that in turn relies on another package. For example, if Contoso publishes a package `Contoso.Utility` which, in turn, depends on `Contoso.Internals` and you add the `Contoso.Utility` package to your project now your project has a direct dependency on `Contoso.Utility` and, because `Contoso.Utility` depends \u0027Contoso.Internals\u0027, your application gains a transitive dependency on the `Contoso.Internals` package.\n\nTransitive dependencies are reviewable in two ways:\n\n* In the Visual Studio Solution Explorer window, which supports searching.\n* By examining the `project.assets.json` file contained in the obj directory of your project for `csproj` based projects\n\nThe `project.assets.json` files are the authoritative list of all packages used by your project, containing both direct and transitive dependencies.\n\nThere are two ways to view transitive dependencies. You can either [use Visual Studio\u2019s Solution Explorer](#vs-solution-explorer), or you can review [the `project.assets.json` file](#project-assets-json)).\n\n##### \u003ca name=\"vs-solution-explorer\"\u003e\u003c/a\u003eUsing Visual Studio Solution Explorer\n\nTo use Solution Explorer, open the project in Visual Studio, and then press Ctrl+; to activate the search in Solution Explorer. Search for the [vulnerable package](#affected-software) and make a note of the version numbers of any results you find.\n\nFor example, search for `Microsoft.AspNetCore.Authentication.JwtBearer` and update the package to the latest version\n\n\n##### \u003ca name=\"project-assets-json\"\u003e\u003c/a\u003e Manually reviewing project.assets.json\n\nOpen the *project.assets.json* file from your project\u2019s obj directory in your editor. We suggest you use an editor that understands JSON and allows you to collapse and expand nodes to review this file.\nVisual Studio and Visual Studio Code provide JSON friendly editing.\n\nSearch the *project.assets.json* file for the [vulnerable package](#affected-software), using the format `packagename/` for each of the package names from the preceding table. If you find the assembly name in your search:\n\n* Examine the line on which they are found, the version number is after the `/`.\n* Compare to the [vulnerable versions table](#affected-software).\n\nFor example, a search result that shows `Microsoft.AspNetCore.Authentication.JwtBearer/2.1.0` is a reference to version 2.1.1 of `Microsoft.AspNetCore.Authentication.JwtBearer`.\n\nIf your *project.assets.json* file includes references to the [vulnerable package](#affected-software), then you need to fix the transitive dependencies.\n\nIf you have not found any reference to any vulnerable packages, this means either\n\n* None of your direct dependencies depend on any vulnerable packages, or\n* You have already fixed the problem by updating the direct dependencies.\n\n#### Other Details\n\n- Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/195\n- An Issue for this can be found at https://github.com/dotnet/aspnetcore/issues/35246\n- MSRC details for this can be found at https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-34532\n", "id": "GHSA-q7cg-43mg-qp69", "modified": "2022-08-11T14:54:06Z", "published": "2021-08-25T14:45:28Z", "references": [ { "type": "WEB", "url": "https://github.com/dotnet/aspnetcore/security/advisories/GHSA-q7cg-43mg-qp69" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-34532" }, { "type": "PACKAGE", "url": "https://github.com/dotnet/aspnetcore" }, { "type": "WEB", "url": "https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2021-34532" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ], "summary": "ASP.NET Core Information Disclosure Vulnerability" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.