OpenTelemetry Rust: Unbounded memory allocation in W3C Baggage propagation
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-rust | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Opentelemetry | Opentelemetry-rust |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-w9wp-h8wv-79jx | opentelemetry_sdk has unbounded memory allocation in W3C Baggage propagation |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.418% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opentelemetry
Opentelemetry opentelemetry-rust |
|
| Vendors & Products |
Opentelemetry
Opentelemetry opentelemetry-rust |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenTelemetry Rust is the Rust OpenTelemetry implementation. In 0.32.0 and earlier, BaggagePropagator::extract_with_context in opentelemetry_sdk did not enforce W3C Baggage size limits before parsing an inbound baggage header, so a large attacker-controlled header could cause unnecessary CPU work and short-lived heap allocations while parsing entries later discarded by the SDK's baggage storage limits. Services that accept untrusted inbound propagation headers may experience increased per-request resource usage when processing oversized baggage headers. This issue is fixed in version 0.32.1. | |
| Title | OpenTelemetry Rust: Unbounded memory allocation in W3C Baggage propagation | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV3_1
|