Advisory record · GHSA-rfxf-mf63-cpqv

open-telemetry has an Observable Timing Discrepancy

CVSS 6.5 MediumEPSS 0.0062 · 49th percentile

Published by the GitHub Advisory Database at 13 Aug 2024, 18:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextensionGo>=0.80.0, <0.107.00.107.0
Identifiers
GHSA-rfxf-mf63-cpqv · CVE-2024-42368 · GO-2024-3066
Weakness (CWE)
CWE-208
Published
13 Aug 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Go module github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension is affected in versions from 0.80.0 before 0.107.0. A client with network access to a collector using the bearertokenauth server authenticator could use a timing attack, measuring response times while sending candidate tokens, to guess the configured token. Upgrade to version 0.107.0 or later. If you cannot upgrade, stop exposing the affected receiver to untrusted networks or switch to a different authentication extension.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0062, the 49th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:15 UTC First seen by agentprime
  2. 31 Oct 2026, 14:15 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.