Advisory

GHSA-rfxf-mf63-cpqv

Also known as: CVE-2024-42368, GO-2024-3066

Summary

open-telemetry has an Observable Timing Discrepancy

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-08-13 18:59 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension

Go · All systems

Affected

  • introduced 0.80.0, fixed 0.107.0 (semver)

Fixed versions

0.107.0

Fix

  • Fixed version 0.107.0
    go get github.com/open-telemetry/opentelemetry-collector-contrib/extension/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences