Skip to content
Fencer Intel
medium 6.5

CVE-2024-42368 json

open-telemetry has an Observable Timing Discrepancy

published 2y ago modified 2mo ago also EUVD-2024-2648 , GHSA-rfxf-mf63-cpqv , GO-2024-3066

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

OpenTelemetry, also known as OTel, is a vendor-neutral open source Observability framework for instrumenting, generating, collecting, and exporting telemetry data such as traces, metrics, and logs. The bearertokenauth extension's server authenticator performs a simple, non-constant time string comparison of the received & configured bearer tokens. This impacts anyone using the `bearertokenauth` server authenticator. Malicious clients with network access to the collector may perform a timing attack against a collector with this authenticator to guess the configured token, by iteratively sending tokens and comparing the response time. This would allow an attacker to introduce fabricated or bad data into the collector's telemetry pipeline. The observable timing vulnerability was fixed by using constant-time comparison in 0.107.0

Patch / fix

  • go github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension 0.107.0
  • opentelemetry opentelemetry_collector_contrib 0.107.0

Is CVE-2024-42368 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-42368 updated cvss 6.5

bearertokenauthextension: Observable Timing Discrepancy in github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension

  • Red Hat Enterprise Linux 9 opentelemetry-collector
    affected: workaround, no fix available
  • Red Hat OpenShift distributed tracing 3.3 rhosdt/tempo-rhel8 2.5.0-4, rhosdt/tempo-query-rhel8 0.13.0-1, rhosdt/jaeger-agent-rhel8 1.57.0-10, rhosdt/jaeger-query-rhel8 1.57.0-11, rhosdt/tempo-gateway-rhel8 1.0.0-17, rhosdt/tempo-rhel8-operator 0.13.0-1, +13 more
    fixed: vendor fix RHSA-2024:6274

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension
>=0.80.0, <0.107.0
0.107.0

Affected products

  • open-telemetry opentelemetry-collector-contrib
  • opentelemetry opentelemetry_collector_contrib

Classification

Weakness
  • CWE-208 Observable Timing Discrepancy

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.