Cross-platform .NET sample microservices and container based application that runs on Linux Windows and macOS. Powered by .NET 6, Docker Containers and Azure Kubernetes Services. Supports Visual Studio, VS for Mac and CLI based environments with Docker CLI, dotnet CLI, VS Code or any other code editor.
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
### Impact
When this library is used to deserialize messagepack data from an untrusted source, there is a risk of a denial of service attack by an attacker that sends data contrived to produce hash collisions, leading to large CPU consumption disproportionate to the size of the data being deserialized.
This is similar to [a prior advisory](https://github.com/MessagePack-CSharp/MessagePack-CSharp/security/advisories/GHSA-7q36-4xx7-xcxf), which provided an inadequate fix for the hash collision part of the vulnerability.
### Patches
The following steps are required to mitigate this risk.
1. Upgrade to a version of the library where a fix is available.
1. Review the steps in [this previous advisory](https://github.com/MessagePack-CSharp/MessagePack-CSharp/security/advisories/GHSA-7q36-4xx7-xcxf) to ensure you have your application configured for untrusted data.
### Workarounds
If upgrading MessagePack to a patched version is not an option for you, you may apply a manual workaround as follows:
1. Declare a class that derives from `MessagePackSecurity`.
2. Override the `GetHashCollisionResistantEqualityComparer` method to provide a collision-resistant hash function of your own and avoid calling `base.GetHashCollisionResistantEqualityComparer()`.
3. Configure a `MessagePackSerializerOptions` with an instance of your derived type by calling `WithSecurity` on an existing options object.
4. Use your custom options object for all deserialization operations. This may be by setting the `MessagePackSerializer.DefaultOptions` static property, if you call methods that rely on this default property, and/or by passing in the options object explicitly to any `Deserialize` method.
### References
- Learn more about best security practices when reading untrusted data with [MessagePack 1.x](https://github.com/MessagePack-CSharp/MessagePack-CSharp/tree/v1.x#security) or [MessagePack 2.x](https://github.com/MessagePack-CSharp/MessagePack-CSharp#security).
- The .NET team's [discussion on hash collision vulnerabilities of their `HashCode` struct](https://github.com/GrabYourPitchforks/runtime/blob/threat_models/docs/design/security/System.HashCode.md).
### For more information
If you have any questions or comments about this advisory:
* [Start a public discussion](https://github.com/MessagePack-CSharp/MessagePack-CSharp/discussions)
* [Email us privately](mailto:andrewarnott@live.com)
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2023-35391
### Vulnerable Library - microsoft.aspnetcore.signalr.stackexchangeredis.6.0.0.nupkg
Provides scale-out support for ASP.NET Core SignalR using a Redis server and the StackExchange.Redis...
Provides scale-out support for ASP.NET Core SignalR using a Redis server and the StackExchange.Redis...
Library home page: https://api.nuget.org/packages/microsoft.aspnetcore.signalr.stackexchangeredis.6.0.0.nupkg
Path to dependency file: /src/Services/Ordering/Ordering.SignalrHub/Ordering.SignalrHub.csproj
Path to vulnerable library: /ages/microsoft.aspnetcore.signalr.stackexchangeredis/6.0.0/microsoft.aspnetcore.signalr.stackexchangeredis.6.0.0.nupkg
Found in HEAD commit: 58162be7965e66c71394dab67f66ed3d7cfaaef5
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2024-48924
### Vulnerable Library - messagepack.2.1.90.nupkgExtremely Fast MessagePack(MsgPack) Serializer for C#(.NET, .NET Core, Unity, Xamarin).
Library home page: https://api.nuget.org/packages/messagepack.2.1.90.nupkg
Path to dependency file: /src/Services/Ordering/Ordering.SignalrHub/Ordering.SignalrHub.csproj
Path to vulnerable library: /home/wss-scanner/.nuget/packages/messagepack/2.1.90/messagepack.2.1.90.nupkg
Dependency Hierarchy: - microsoft.aspnetcore.signalr.stackexchangeredis.6.0.0.nupkg (Root Library) - :x: **messagepack.2.1.90.nupkg** (Vulnerable Library)
Found in HEAD commit: 58162be7965e66c71394dab67f66ed3d7cfaaef5
Found in base branch: dev
### Vulnerability Details### Impact When this library is used to deserialize messagepack data from an untrusted source, there is a risk of a denial of service attack by an attacker that sends data contrived to produce hash collisions, leading to large CPU consumption disproportionate to the size of the data being deserialized. This is similar to [a prior advisory](https://github.com/MessagePack-CSharp/MessagePack-CSharp/security/advisories/GHSA-7q36-4xx7-xcxf), which provided an inadequate fix for the hash collision part of the vulnerability. ### Patches The following steps are required to mitigate this risk. 1. Upgrade to a version of the library where a fix is available. 1. Review the steps in [this previous advisory](https://github.com/MessagePack-CSharp/MessagePack-CSharp/security/advisories/GHSA-7q36-4xx7-xcxf) to ensure you have your application configured for untrusted data. ### Workarounds If upgrading MessagePack to a patched version is not an option for you, you may apply a manual workaround as follows: 1. Declare a class that derives from `MessagePackSecurity`. 2. Override the `GetHashCollisionResistantEqualityComparer` method to provide a collision-resistant hash function of your own and avoid calling `base.GetHashCollisionResistantEqualityComparer()`.
3. Configure a `MessagePackSerializerOptions` with an instance of your derived type by calling `WithSecurity` on an existing options object.
4. Use your custom options object for all deserialization operations. This may be by setting the `MessagePackSerializer.DefaultOptions` static property, if you call methods that rely on this default property, and/or by passing in the options object explicitly to any `Deserialize` method.
### References
- Learn more about best security practices when reading untrusted data with [MessagePack 1.x](https://github.com/MessagePack-CSharp/MessagePack-CSharp/tree/v1.x#security) or [MessagePack 2.x](https://github.com/MessagePack-CSharp/MessagePack-CSharp#security).
- The .NET team's [discussion on hash collision vulnerabilities of their `HashCode` struct](https://github.com/GrabYourPitchforks/runtime/blob/threat_models/docs/design/security/System.HashCode.md).
### For more information
If you have any questions or comments about this advisory:
* [Start a public discussion](https://github.com/MessagePack-CSharp/MessagePack-CSharp/discussions)
* [Email us privately](mailto:andrewarnott@live.com)
### CVSS 3 Score Details (7.5)Publish Date: 2024-10-17
URL: CVE-2024-48924
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/MessagePack-CSharp/MessagePack-CSharp/security/advisories/GHSA-4qm4-8hg2-g2xm
Release Date: 2024-10-17
Fix Resolution: MessagePack - 2.5.187,3.0.214-rc.1
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
CVE-2023-35391
### Vulnerable Library - microsoft.aspnetcore.signalr.stackexchangeredis.6.0.0.nupkgProvides scale-out support for ASP.NET Core SignalR using a Redis server and the StackExchange.Redis...
Library home page: https://api.nuget.org/packages/microsoft.aspnetcore.signalr.stackexchangeredis.6.0.0.nupkg
Path to dependency file: /src/Services/Ordering/Ordering.SignalrHub/Ordering.SignalrHub.csproj
Path to vulnerable library: /ages/microsoft.aspnetcore.signalr.stackexchangeredis/6.0.0/microsoft.aspnetcore.signalr.stackexchangeredis.6.0.0.nupkg
Dependency Hierarchy: - :x: **microsoft.aspnetcore.signalr.stackexchangeredis.6.0.0.nupkg** (Vulnerable Library)
Found in HEAD commit: 58162be7965e66c71394dab67f66ed3d7cfaaef5
Found in base branch: dev
### Vulnerability DetailsASP.NET Core SignalR and Visual Studio Information Disclosure Vulnerability
Publish Date: 2023-08-08
URL: CVE-2023-35391
### CVSS 3 Score Details (6.2)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-j8rm-cm55-qqj6
Release Date: 2023-08-08
Fix Resolution: Microsoft.AspNetCore.SignalR.Redis - 1.0.40, Microsoft.AspNetCore.SignalR.StackExchangeRedis - 6.0.21,7.0.10
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)