Medium, CVSS 6.9GoPublished
open-telemetry has an Observable Timing Discrepancy
CVE-2024-42368 · GHSA-rfxf-mf63-cpqv
- Affected
- Go github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension >= 0.80.0, < 0.107.0
- Fixed in
- 0.107.0· Vendor fix available
- Issue
- 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…
Recommended action: Upgrade to 0.107.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.