Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
The implementation details of the baggage, B3 and Jaeger processing code in the OpenTelemetry.Api and OpenTelemetry.Extensions.Propagators NuGet packages can allocate excessive memory when parsing which could create a potential denial of service (DoS) in the consuming application. Details Exceeding Limits BaggagePropagator.Inject<T() does not enforce the length limit of 8192 characters if the injected baggage contains only one item. This change was introduced by #1048. Excessive allocation The following methods eagerly allocate intermediate arrays before applying size limits. - BaggagePropagator.Extract<T() - this change was introduced by #1048. - BaggagePropagator.Inject<T() - this change was introduced by #1048. - B3Propagator.Extract<T() - this change was introduced by #533. - B3Propagator.Extract<T() - this change was introduced by #3244. - JaegerPropagator.Extract<T() - this change was introduced by #3309. Impact Excessively large propagation headers, particularly in…
Recommended action: Upgrade to 1.15.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact 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. 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. Patches Has the problem been patched? What versions should users upgrade to? This issue has been <strong data-start="1143" data-end="1184"resolved in OpenTelemetry.Api 1.11.2</strong by <strong data-start="1188" data-end="1212"reverting the change</strong that introduced the problematic behavior in versions <strong data-start="1266" data-end="1286"1.10.0 to 1.11.1</strong.</li<li…
Recommended action: Upgrade to 1.11.2; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.