OpenTelemetry Python: Unbounded memory allocation in Jaeger baggage propagation

[ Description ]Official description

OpenTelemetry Python provides the Python API and SDK for OpenTelemetry. Prior to 1.45.0, JaegerPropagator.extract() in opentelemetry-propagator-jaeger processes inbound uberctx-* baggage values without entry, per-entry byte, or total-byte limits. Services that enable the optional Jaeger propagator can perform unnecessary CPU work and short-lived heap allocations when an untrusted carrier supplies numerous or oversized values, contributing to denial of service when transport-level limits do not constrain the input. Common default Python HTTP server limits reduce the practical impact, while custom getters, non-HTTP transports, or raised header limits increase exposure. This issue is fixed in version 1.45.0.

[ Fixes ]Fixes and patches

• opentelemetry-propagator-jaeger 1.45.0Fixed version · GitHub Advisories · pip package opentelemetry-propagator-jaeger: upgrade to 1.45.0 or later (affected <= 1.44.0)

[ Packages ]Affected open-source packages

• opentelemetry-propagator-jaeger pipAffected <= 1.44.0 · fixed in 1.45.0 · GHSA-f5m9-jfrj-jjj7

[ References ]References

• github.com/open-telemetry/opentelemetry-python/commit/65c4eeb87cd3815dc795d3b5485e9ea0d…
• github.com/open-telemetry/opentelemetry-python/pull/5556
• github.com/open-telemetry/opentelemetry-python/releases/tag/v1.45.0
• github.com/open-telemetry/opentelemetry-python/security/advisories/GHSA-f5m9-jfrj-jjj7