OpenTelemetry-Go: Unsynchronized baggage map can panic under concurrent access
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| open-telemetry | opentelemetry-go | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Opentelemetry | Opentelemetry-go |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-42cj-99w8-cp2p | OpenTelemetry-Go: Unsynchronized baggage map can panic under concurrent access |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.139% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-820 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opentelemetry
Opentelemetry opentelemetry-go |
|
| Vendors & Products |
Opentelemetry
Opentelemetry opentelemetry-go |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 0.11.0 through 1.44.0, the OpenTracing bridge's bridgeSpan contains an unsynchronized extraBaggageItems map which can cause a panic. Because Go maps are not safe for concurrent read/write access, concurrent SetBaggageItem and correlation.MapFromContext calls on the same hooked bridgeSpan can trigger a fatal runtime error—such as concurrent map read and map write or concurrent map iteration and map write—terminating the process and causing denial of service. This issue is fixed in version 1.45.0. | |
| Title | OpenTelemetry-Go: Unsynchronized baggage map can panic under concurrent access | |
| Weaknesses | CWE-362 CWE-667 |
|
| References |
|
|
| Metrics |
cvssV4_0
|