OpenTelemetry Python: Unbounded memory allocation in Jaeger baggage propagation

Why it is Yellow

• CVSS 6.3 medium
• On your watchlist: python, PyPI

Affected packages

References

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

Original 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.