dd-trace-go: Improper parsing of W3C baggage headers may lead to DoS
DataDog dd-trace-go
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/DataDog/dd-trace-go Go |
| No fix yet |
| github.com/DataDog/dd-trace-go/v2 Go |
|
|
DataDog dd-trace-go
| Product | Affected | Fixed in |
|---|---|---|
| github.com/DataDog/dd-trace-go Go |
| No fix yet |
| github.com/DataDog/dd-trace-go/v2 Go |
|
|
Datadog dd-trace-go is a Go client library for Datadog application performance monitoring, profiling, and security monitoring. Prior to 2.8.1, 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 limits on the extract path. A remote, unauthenticated attacker can send a request whose baggage header contains an arbitrarily large number of comma-separated key-value pairs or a single very large value, causing unbounded CPU and memory consumption and enabling a remote denial of service against HTTP services with baggage propagation enabled. This issue is fixed in version 2.8.1.
From the CVE record · GitHub_M
With W3C baggage propagation enabled, dd-trace-go parses incoming baggage HTTP headers without enforcing item or byte limits. A remote, unauthenticated attacker can send an oversized header to consume unbounded CPU and memory, causing denial of service; no user interaction is needed.
Check HTTP services using github.com/DataDog/dd-trace-go/v2 before 2.8.1 or github.com/DataDog/dd-trace-go at version 1.24.1 or earlier; the latter package has no fixed version listed.