## Summary The parameterless `MessagePackInputFormatter()` constructor uses default serializer options, which resolve to `MessagePackSerializerOptions.Standard` with `MessagePackSecurity.TrustedData`. The formatter is designed for ASP.NET Core MVC request bodies, which commonly cross an HTTP trust boundary. This insecure default can expose applications to denial-of-service attacks that `MessagePackSecurity.UntrustedData` is intended to mitigate, such as hash-collision attacks against dictionary-like model properties. ## Impact Applications are affected when they register `new MessagePackInputFormatter()` without explicitly passing serializer options configured for untrusted data. An unauthenticated or otherwise untrusted HTTP client can send MessagePack request bodies that are deserialized using the trusted-data posture. For models containing hash-based collections, this can enable algorithmic complexity attacks using colliding keys. The default constructor makes the unsafe posture easy to use at the exact boundary where request bodies should be treated as untrusted. ## Affected components - Package: `MessagePack.AspNetCoreMvcFormatter` - API: `MessagePackInputFormatter()` parameterless constructor - Scenario: ASP.NET Core MVC model binding from HTTP request bodies - Finding IDs: `MESSAGEPACKCSHARP-OPEN-009`, duplicate `MESSAGEPACKCSHARP-095` ## Patches Fixes are prepared and will be released in coordinated patch versions. Upgrade guidance: 1. Upgrade `MessagePack.AspNetCoreMvcFormatter` to the patched version for your release line. 2. Upgrade companion MessagePack packages in the same dependency graph to the coordinated patched versions. The fix should default the parameterless constructor to `MessagePackSerializerOptions.Standard.WithSecurity(MessagePackSecurity.UntrustedData)`, or require callers to pass explicit options so the trust posture is deliberate. ## Workarounds Do not use the parameterless constructor on affected versions. Register the formatter with explicit untrusted-data options, for example: ```csharp options.InputFormatters.Add( new MessagePackInputFormatter( MessagePackSerializerOptions.Standard.WithSecurity(MessagePackSecurity.UntrustedData))); ``` Also apply normal HTTP request-size limits and model validation appropriate for your service. ## Resources - `MESSAGEPACKCSHARP-OPEN-009`: MVC input formatter defaults to trusted-data security posture - `MESSAGEPACKCSHARP-095`: duplicate finding for the same root cause - CWE-1188: Initialization of a Resource with an Insecure Default
## Summary The parameterless `MessagePackInputFormatter()` constructor uses default serializer options, which resolve to `MessagePackSerializerOptions.Standard` with `MessagePackSecurity.TrustedData`. The formatter is designed for ASP.NET Core MVC request bodies, which commonly cross an HTTP trust boundary. This insecure default can expose applications to denial-of-service attacks that `MessagePackSecurity.UntrustedData` is intended to mitigate, such as hash-collision attacks against dictionary-like model properties. ## Impact Applications are affected when they register `new MessagePackInputFormatter()` without explicitly passing serializer options configured for untrusted data. An unauthenticated or otherwise untrusted HTTP client can send MessagePack request bodies that are deserialized using the trusted-data posture. For models containing hash-based collections, this can enable algorithmic complexity attacks using colliding keys. The default constructor makes the unsafe posture easy to use at the exact boundary where request bodies should be treated as untrusted. ## Affected components - Package: `MessagePack.AspNetCoreMvcFormatter` - API: `MessagePackInputFormatter()` parameterless constructor - Scenario: ASP.NET Core MVC model binding from HTTP request bodies - Finding IDs: `MESSAGEPACKCSHARP-OPEN-009`, duplicate `MESSAGEPACKCSHARP-095` ## Patches Fixes are prepared and will be released in coordinated patch versions. Upgrade guidance: 1. Upgrade `MessagePack.AspNetCoreMvcFormatter` to the patched version for your release line. 2. Upgrade companion MessagePack packages in the same dependency graph to the coordinated patched versions. The fix should default the parameterless constructor to `MessagePackSerializerOptions.Standard.WithSecurity(MessagePackSecurity.UntrustedData)`, or require callers to pass explicit options so the trust posture is deliberate. ## Workarounds Do not use the parameterless constructor on affected versions. Register the formatter with explicit untrusted-data options, for example: ```csharp options.InputFormatters.Add( new MessagePackInputFormatter( MessagePackSerializerOptions.Standard.WithSecurity(MessagePackSecurity.UntrustedData))); ``` Also apply normal HTTP request-size limits and model validation appropriate for your service. ## Resources - `MESSAGEPACKCSHARP-OPEN-009`: MVC input formatter defaults to trusted-data security posture - `MESSAGEPACKCSHARP-095`: duplicate finding for the same root cause - CWE-1188: Initialization of a Resource with an Insecure Default
Update MessagePack to 2.5.301; MessagePack to 3.1.7 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanMessagePack-CSharp: ASP.NET Core MessagePackInputFormatter defaults to TrustedData for HTTP request bodies affects MessagePack (nuget), MessagePack (nuget). Severity is critical. ## Summary The parameterless `MessagePackInputFormatter()` constructor uses default serializer options, which resolve to `MessagePackSerializerOptions.Standard` with `MessagePackSecurity.TrustedData`. The formatter is designed for ASP.NET Core MVC request bodies, which commonly cross an HTTP trust boundary. This insecure default can expose applications to denial-of-service attacks that `MessagePackSecurity.UntrustedData` is intended to mitigate, such as hash-collision attacks against dictionary-like model properties. ## Impact Applications are affected when they register `new MessagePackInputFormatter()` without explicitly passing serializer options configured for untrusted data. An unauthenticated or otherwise untrusted HTTP client can send MessagePack request bodies that are deserialized using the trusted-data posture. For models containing hash-based collections, this can enable algorithmic complexity attacks using colliding keys. The default constructor makes the unsafe posture easy to use at the exact boundary where request bodies should be treated as untrusted. ## Affected components - Package: `MessagePack.AspNetCoreMvcFormatter` - API: `MessagePackInputFormatter()` parameterless constructor - Scenario: ASP.NET Core MVC model binding from HTTP request bodies - Finding IDs: `MESSAGEPACKCSHARP-OPEN-009`, duplicate `MESSAGEPACKCSHARP-095` ## Patches Fixes are prepared and will be released in coordinated patch versions. Upgrade guidance: 1. Upgrade `MessagePack.AspNetCoreMvcFormatter` to the patched version for your release line. 2. Upgrade companion MessagePack packages in the same dependency graph to the coordinated patched versions. The fix should default the parameterless constructor to `MessagePackSerializerOptions.Standard.WithSecurity(MessagePackSecurity.UntrustedData)`, or require callers to pass explicit options so the trust posture is deliberate. ## Workarounds Do not use the parameterless constructor on affected versions. Register the formatter with explicit untrusted-data options, for example: ```csharp options.InputFormatters.Add( new MessagePackInputFormatter( MessagePackSerializerOptions.Standard.WithSecurity(MessagePackSecurity.UntrustedData))); ``` Also apply normal HTTP request-size limits and model validation appropriate for your service. ## Resources - `MESSAGEPACKCSHARP-OPEN-009`: MVC input formatter defaults to trusted-data security posture - `MESSAGEPACKCSHARP-095`: duplicate finding for the same root cause - CWE-1188: Initialization of a Resource with an Insecure Default
AI coding agents often install or upgrade packages automatically in nuget. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| MessagePacknuget | <2.5.301 | 2.5.301 |
| MessagePacknuget | >=3.0,<3.1.7 | 3.1.7 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate MessagePack to 2.5.301; MessagePack to 3.1.7 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanMessagePack-CSharp: ASP.NET Core MessagePackInputFormatter defaults to TrustedData for HTTP request bodies affects MessagePack (nuget), MessagePack (nuget). Severity is critical. ## Summary The parameterless `MessagePackInputFormatter()` constructor uses default serializer options, which resolve to `MessagePackSerializerOptions.Standard` with `MessagePackSecurity.TrustedData`. The formatter is designed for ASP.NET Core MVC request bodies, which commonly cross an HTTP trust boundary. This insecure default can expose applications to denial-of-service attacks that `MessagePackSecurity.UntrustedData` is intended to mitigate, such as hash-collision attacks against dictionary-like model properties. ## Impact Applications are affected when they register `new MessagePackInputFormatter()` without explicitly passing serializer options configured for untrusted data. An unauthenticated or otherwise untrusted HTTP client can send MessagePack request bodies that are deserialized using the trusted-data posture. For models containing hash-based collections, this can enable algorithmic complexity attacks using colliding keys. The default constructor makes the unsafe posture easy to use at the exact boundary where request bodies should be treated as untrusted. ## Affected components - Package: `MessagePack.AspNetCoreMvcFormatter` - API: `MessagePackInputFormatter()` parameterless constructor - Scenario: ASP.NET Core MVC model binding from HTTP request bodies - Finding IDs: `MESSAGEPACKCSHARP-OPEN-009`, duplicate `MESSAGEPACKCSHARP-095` ## Patches Fixes are prepared and will be released in coordinated patch versions. Upgrade guidance: 1. Upgrade `MessagePack.AspNetCoreMvcFormatter` to the patched version for your release line. 2. Upgrade companion MessagePack packages in the same dependency graph to the coordinated patched versions. The fix should default the parameterless constructor to `MessagePackSerializerOptions.Standard.WithSecurity(MessagePackSecurity.UntrustedData)`, or require callers to pass explicit options so the trust posture is deliberate. ## Workarounds Do not use the parameterless constructor on affected versions. Register the formatter with explicit untrusted-data options, for example: ```csharp options.InputFormatters.Add( new MessagePackInputFormatter( MessagePackSerializerOptions.Standard.WithSecurity(MessagePackSecurity.UntrustedData))); ``` Also apply normal HTTP request-size limits and model validation appropriate for your service. ## Resources - `MESSAGEPACKCSHARP-OPEN-009`: MVC input formatter defaults to trusted-data security posture - `MESSAGEPACKCSHARP-095`: duplicate finding for the same root cause - CWE-1188: Initialization of a Resource with an Insecure Default
AI coding agents often install or upgrade packages automatically in nuget. A critical vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| MessagePacknuget | <2.5.301 | 2.5.301 |
| MessagePacknuget | >=3.0,<3.1.7 | 3.1.7 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard