fix(#2387): bump opentelemetry-api 1.51.0 → 1.62.0 (W3C Baggage CVE)#52
Merged
Conversation
Dependabot alert #5: io.opentelemetry:opentelemetry-api <= 1.61.0 allows unbounded memory allocation and CPU consumption when parsing oversized baggage headers in W3CBaggagePropagator, JaegerPropagator, and OtTracePropagator. Because baggage auto-re-injects into outgoing requests, a single malicious header fans out across the downstream graph. 1.62.0 enforces caps consistent with the W3C Baggage spec at the propagator level: 8,192 bytes total, 64 entries. Over-limit headers are dropped at the cap point; already-extracted valid entries are retained. Practical exposure for Agents.KT is limited — we expose OpenTelemetry only through the `:agents-kt-otel` adapter, and the adapter emits spans rather than parsing inbound baggage. Risk applies to downstream consumers who enable baggage propagation in their own SDK pipeline, especially on non-HTTP transports where transport-layer header limits don't apply. The fix is a version bump: - agents-kt-otel/build.gradle.kts: 1.51.0 → 1.62.0 on both the production `opentelemetry-api` dependency and the testImplementation `opentelemetry-sdk-trace`. - gradle/verification-metadata.xml: refreshed via `./gradlew updateVerificationMetadata` for the four pinned OTel components (api, context, sdk-common, sdk-trace) plus the new transitive `opentelemetry-common` 1.62.0. Stale 1.51.0 entries removed so the metadata file remains the authoritative current state. `./gradlew :agents-kt-otel:test`: 7/7 green. No API surface changes between 1.51 and 1.62 affect our use; the adapter compiles + behaves unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dependabot alert #5: io.opentelemetry:opentelemetry-api <= 1.61.0 allows unbounded memory allocation and CPU consumption when parsing oversized baggage headers in W3CBaggagePropagator, JaegerPropagator, and OtTracePropagator. Because baggage auto-re-injects into outgoing requests, a single malicious header fans out across the downstream graph.
1.62.0 enforces caps consistent with the W3C Baggage spec at the propagator level: 8,192 bytes total, 64 entries. Over-limit headers are dropped at the cap point; already-extracted valid entries are retained.
Practical exposure for Agents.KT is limited — we expose OpenTelemetry only through the
:agents-kt-oteladapter, and the adapter emits spans rather than parsing inbound baggage. Risk applies to downstream consumers who enable baggage propagation in their own SDK pipeline, especially on non-HTTP transports where transport-layer header limits don't apply.The fix is a version bump:
opentelemetry-apidependency and the testImplementationopentelemetry-sdk-trace../gradlew updateVerificationMetadatafor the four pinned OTel components (api, context, sdk-common, sdk-trace) plus the new transitiveopentelemetry-common1.62.0. Stale 1.51.0 entries removed so the metadata file remains the authoritative current state../gradlew :agents-kt-otel:test: 7/7 green. No API surface changes between 1.51 and 1.62 affect our use; the adapter compiles + behaves unchanged.