CVE-2024-42368 open-telemetry has an Observable Timing Discrepancy

What is CVE-2024-42368?

CVE-2024-42368 is a medium-severity vulnerability in open-telemetry opentelemetry-collector-contrib, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

OpenTelemetry, also known as OTel, is a vendor-neutral open source Observability framework for instrumenting, generating, collecting, and exporting telemetry data such as traces, metrics, and logs. The bearertokenauth extension's server authenticator performs a simple, non-constant time string comparison of the received & configured bearer tokens. 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. The observable timing vulnerability was fixed by using constant-time comparison in 0.107.0

Weakness: CWE-208

Which versions are affected by CVE-2024-42368?

3 open source packages ship an affected version, including github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension.

How do I fix CVE-2024-42368?

Upgrade github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension to 0.107.0 or later.

Is CVE-2024-42368 being exploited?

There is no known exploitation of CVE-2024-42368 in the wild and no public exploit code.

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-rfxf-mf63-cpqv, GO-2024-3066.