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 global propagator.
What happened
Reportedly, the @opentelemetry/propagator-jaeger npm package decodes incoming HTTP header values without handling decode errors, which appears to lead to a denial of service when a malformed percent-encoded value is encountered. This issue is under investigation and the severity is assessed as high. Services utilizing JaegerPropagator as the global propagator may be at risk.
To assess your exposure, check if your services are using the @opentelemetry/propagator-jaeger package in a version prior to 2.9.0. The recommended action is to update to version 2.9.0 or later to mitigate the risk of denial of service attacks. For more detailed information, consult the primary sources listed below.
Primary sources should be consulted for the most accurate and up-to-date information on this potential vulnerability. The specific details and affected version ranges can be found in the GitHub Security Advisory [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.