What kind of vulnerability is it? Who is impacted?
A vulnerability in OpenTelemetry.Api
package 1.10.0
to 1.11.1
could cause a Denial of Service (DoS) when a tracestate and traceparent header is received. These versions are used in OpenTelemetry .NET Automatic Instrumentation 1.10.0-beta.1
and 1.10.0
.
Even if an application does not explicitly use trace context propagation, receiving these headers can still trigger high CPU usage. This issue impacts any application accessible over the web or backend services that process HTTP requests containing a tracestate header. Application may experience excessive resource consumption, leading to increased latency, degraded performance, or downtime.
Has the problem been patched? What versions should users upgrade to?
This issue has been resolved in OpenTelemetry.Api
1.11.2
by reverting the change that introduced the problematic behavior in versions 1.10.0
to 1.11.1
. OpenTelemetry .NET Automatic Instrumentation fixes it in 1.11.0
release.
| OpenTelemetry .NET Automatic Instrumentation | Status | |----|----| | <= 1.9.0 | ✅ Not affected | | 1.10.0-beta.1, 1.10.0 | ❌ Vulnerable | | 1.11.0 (Fixed)| ✅ Safe to use|
Is there a way for users to fix or remediate the vulnerability without upgrading?
Are there any links users can visit to find out more?
{ "nvd_published_at": null, "cwe_ids": [ "CWE-770" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2025-03-06T22:33:43Z" }