OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| open-telemetry | opentelemetry-go | affected |
|
No data.
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-rrfc-gjm9-cgrj | OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | OpenTelemetry-Go: Eager W3C baggage-property materialization causes bounded memory-allocation amplification | |
| Weaknesses | CWE-400 CWE-405 |
|
| References |
|
|
| Metrics |
cvssV3_1
|
No data.