Update dependency Microsoft.AspNetCore.SignalR.StackExchangeRedis to 6.0.21 [SECURITY] #177
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.0.6
->6.0.21
GitHub Vulnerability Alerts
CVE-2023-35391
Microsoft Security Advisory CVE-2023-35391: .NET Information Disclosure Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET core 2.1, .NET 6.0 and, .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A vulnerability exists in ASP.NET Core 2.1, .NET 6.0 and, .NET 7.0 applications using SignalR when redis backplane use might result in information disclosure.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/267
Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET.
.NET 7
.NET 6
ASP.NET Core 2.1
Advisory FAQ
How do I know if I am affected?
If you have a runtime or SDK with a version listed, or an affected package listed in affected software, you're exposed to the vulnerability.
How do I fix the issue?
dotnet --info
command. You will see output like the following;.NET 6.0 and and .NET 7.0 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
Other Information
Reporting Security Issues
If you have found a potential security issue in .NET 6.0 or .NET 7.0, please email details to [email protected]. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
External Links
CVE-2023-35391
Revisions
V1.0 (August 08, 2023): Advisory published.
Version 1.0
Last Updated 2023-08-08
Release Notes
dotnet/aspnetcore (Microsoft.AspNetCore.SignalR.StackExchangeRedis)
v6.0.21
: .NET 6.0.21Release
v6.0.20
: .NET 6.0.20Release
v6.0.19
: .NET 6.0.19Release
v6.0.18
: .NET 6.0.18Release
v6.0.16
: .NET 6.0.16Release
v6.0.15
: .NET 6.0.15Release
v6.0.14
: .NET 6.0.14Release
v6.0.13
: .NET 6.0.13Release
v6.0.12
: .NET 6.0.12Release
v6.0.11
: .NET 6.0.11Release
v6.0.10
: .NET 6.0.10Release
v6.0.9
: .NET 6.0.9Release
v6.0.8
: .NET 6.0.8Release
v6.0.7
: .NET 6.0.7Release
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.