Answer in brief
CVE-2024-42368 records a Medium severity (CVSS 6.5) vulnerability in open-telemetry has an Observable Timing Discrepancy. The current sources do not mark it as known exploited. The current feed maps github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextensiongo | >=0.80.0 <0.107.0 | 0.107.0 |
Published upstream
Aug 13, 2024
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Sep 10, 2026
### 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 using constant-time comparison. ### Workarounds - upgrade to v0.107.0 or above, or, if you're unable to upgrade at this time, - don't expose the receiver using `bearertokenauth` to network segments accessible by potential attackers, or - change the receiver to use a different authentication extension instead, or - disable the receiver relying on `bearertokenauth`
Quoted source text, attributed separately from HOL analysis.