Potential Denial of Service in OpenTelemetry JaegerPropagator
An early warning has been issued regarding a potential denial of service vulnerability in the @opentelemetry/propagator-jaeger npm package, affecting services using JaegerPropagator as the active propagator.
What happened
Reportedly, the @opentelemetry/propagator-jaeger npm package decodes HTTP header values without handling decode errors, which appears to lead to a denial of service when a malformed header is encountered. This issue is under investigation and affects versions of @opentelemetry/propagator-jaeger prior to 2.9.0.
To assess your exposure, check if your services are using JaegerPropagator as the active propagator and if the @opentelemetry/propagator-jaeger package version is less than 2.9.0. It is recommended to update to version 2.9.0 or later to mitigate the risk of denial of service.
For more detailed information, consult the primary source at [GHSA-45rx-2jwx-cxfr](https://github.com/open-telemetry/opentelemetry-js/security/advisories/GHSA-45rx-2jwx-cxfr).
How 0Day mitigates this
@opentelemetry/propagator-jaeger is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.