Impact
The vulnerability involves an unsynchronized baggage map in OpenTelemetry‑Go’s OpenTracing bridge. When concurrent SetBaggageItem and correlation.MapFromContext calls access the same map, Go’s map concurrency rules are violated, causing a panic that terminates the process. The primary impact is a denial of service, as the application or service using the library crashes. The weakness is a race condition (CWE‑362) and improper synchronization (CWE‑667).
Affected Systems
OpenTelemetry-Go version 0.11.0 through 1.44.0 is affected. The issue appears in the library that implements the OpenTracing bridge. Any application that links to this library and uses the OpenTracing bridge for baggage handling can be impacted.
Risk and Exploitability
The CVSS score of 5.9 signals moderate severity; the EPSS score of < 1% indicates a very low but non-zero likelihood of exploitation. The vulnerability is not in CISA’s KEV catalog, implying no widespread attacks currently reported. The attack vector is inferred to be application‑level concurrent tracing operations; an attacker would need to trigger simultaneous SetBaggageItem and MapFromContext calls on the same span to cause the crash.
OpenCVE Enrichment
Github GHSA