# CVE-2024-42368: open-telemetry has an Observable Timing Discrepancy > Attackers can guess bearer tokens via timing attacks to inject fabricated data into the telemetry pipeline. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Aug 2024 - **Updated:** 14 Aug 2024 - **Also known as:** GHSA-rfxf-mf63-cpqv, GO-2024-3066 ## 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 (Observable Timing Discrepancy) ## 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. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension` | Go | From 0.80.0 | 0.107.0 | | `github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension` | Go | From 0.80.0 | 0.107.0 | | `github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension` | Go | From 0.80.0 | 0.107.0 | ## 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. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-42368 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2024-42368 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension (Go): affected from 0.80.0; fixed in 0.107.0 - github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension (Go): affected from 0.80.0; fixed in 0.107.0 - github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension (Go): affected from 0.80.0; fixed in 0.107.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-42368/ (Markdown: https://insights.sbomify.com/CVE-2024-42368/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-42368 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-42368 - OSV: https://osv.dev/vulnerability/CVE-2024-42368 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-42368/ Summaries are generated and may contain mistakes; the official description above is the record.