open-telemetry has an Observable Timing Discrepancy

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-42368: 0.62% estimated exploitation activity in the next 30 days; percentile 49.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The bearertokenauth extension's server authenticator performs a simple, non-constant time string comparison of the received & configured bearer tokens. Details https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/9128a9258fe1fee36f198f97b1e3371fc7b77a93/extension/bearertokenauthextension/bearertokenauth.go#L189-L196 For background on the type of vulnerability, see https://ropesec.com/articles/timing-attacks/. Impact 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. Fix The observable timing vulnerability was fixed by @axw in v0.107.0 (PR https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34516) by…

Published by the source

13 Aug 2024, 18:59 UTC

Last modified by the source

13 Aug 2024, 21:57 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rfxf-mf63-cpqv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-42368

Advisory: open-telemetry has an Observable Timing Discrepancy
IDs: CVE-2024-42368, GHSA-rfxf-mf63-cpqv
Record: https://patchnext.com/advisories/cve-2024-42368 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension 0.107.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension: affected >= 0.80.0, < 0.107.0; fixed in 0.107.0

## Suggested inspection (read-only)
- Go github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rfxf-mf63-cpqv (GitHub-reviewed advisory GHSA-rfxf-mf63-cpqv lists affected ranges: Go github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension >=0.80.0 <0.107.0)

Commands are suggestions: review each one before running it.