opentelemetry-java: Quadratic CPU consumption in W3C tracestate parsing
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
opentelemetry-java is the Java implementation of the OpenTelemetry API for recording telemetry, and SDK for managing telemetry recorded by the API. Prior to 1.67.0, W3CTraceContextPropagator.extract() uses regex delimiter processing that can exhibit quadratic backtracking while parsing tracestate headers containing long runs of spaces or tabs without a following comma. An unauthenticated attacker whose headers reach extraction can repeatedly block request or event-loop threads and cause excessive CPU consumption, with practical impact bounded by ingress header-size limits, proxy configuration, and threading. This issue is fixed in version 1.67.0.
Text from CVE List
Affected versions 1
- opentelemetry-javaaffected: < 1.67.0CVE List
References 5
- github.com/open-telemetry/opentelemetry-java/commit/ba4dfea91647d1ef596975db5d7197681df3c0f5Fixvia CVE List
- github.com/open-telemetry/opentelemetry-java/commit/cc4f5f22aed0d69369941cde8029e73507cf438fFixvia CVE List
- github.com/open-telemetry/opentelemetry-java/releases/tag/v1.67.0Fixvia CVE List
- github.com/open-telemetry/opentelemetry-java/security/advisories/GHSA-ccrj-gw8r-854mAdvisoryvia CVE List
- github.com/open-telemetry/opentelemetry-java/pull/8914Referencevia CVE List