Datadog .NET Tracer: Improper parsing of W3C baggage headers may lead to DoS
DataDog dd-trace-dotnet
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Datadog.Trace NuGet |
|
|
| Datadog.Trace.OpenTracing NuGet |
|
|
DataDog dd-trace-dotnet
| Product | Affected | Fixed in |
|---|---|---|
| Datadog.Trace NuGet |
|
|
| Datadog.Trace.OpenTracing NuGet |
|
|
Datadog .NET Tracer is a client library for Datadog APM for .NET applications. Prior to 3.43.0, Datadog tracing libraries that implement W3C baggage propagation parse incoming baggage HTTP headers without enforcing DD_TRACE_BAGGAGE_MAX_ITEMS or DD_TRACE_BAGGAGE_MAX_BYTES on extraction, allowing a remote unauthenticated attacker to send a baggage header with many comma-separated key-value pairs or one very large value and cause unbounded CPU and memory consumption in services with baggage propagation enabled. This issue is fixed in version 3.43.0.
From the CVE record · GitHub_M
Before 3.43.0, Datadog .NET tracing libraries do not enforce baggage size or item limits when extracting incoming W3C baggage HTTP headers. A remote, unauthenticated attacker can send an oversized baggage header to cause unbounded CPU and memory consumption in services with baggage propagation enabled; no user interaction is required.
Operators of services using NuGet Datadog.Trace or Datadog.Trace.OpenTracing versions earlier than 3.43.0 should check their deployments.