OpenTelemetry-Go memory exhaustion in baggage parsing
open-telemetry opentelemetry-go
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| go.opentelemetry.io/otel/baggage Go |
|
|
| go.opentelemetry.io/otel/propagation Go |
|
|
open-telemetry opentelemetry-go
| Product | Affected | Fixed in |
|---|---|---|
| go.opentelemetry.io/otel/baggage Go |
|
|
| go.opentelemetry.io/otel/propagation Go |
|
|
OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.0.0-RC1 until version 1.47.0, baggage.Parse and propagation.Baggage.Extract eagerly materialize every W3C baggage property through parseMember, grow property slices, serialize members, and copy properties into internal/baggage.Item. A valid densely populated baggage header can therefore cause allocation traffic and retained memory disproportionate to its bounded input size. Remote impact requires baggage extraction to be enabled, attacker-controlled input to reach it, and extraction to run before authentication or on a public route; the evidence establishes increased allocation and garbage-collection pressure but not reliable process termination. This issue is fixed in version 1.47.0.
From the CVE record · GitHub_M
OpenTelemetry-Go baggage.Parse and propagation.Baggage.Extract can allocate disproportionate memory when processing a densely populated, valid baggage header. A remote attacker can increase allocation and garbage-collection pressure if attacker-controlled input reaches enabled baggage extraction before authentication or on a public route; reliable process termination has not been established.
Check Go services using go.opentelemetry.io/otel/baggage or go.opentelemetry.io/otel/propagation versions >=1.0.0-RC1 and <1.47.0.