Opentelemetry Collector Contrib

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:opentelemetry:opentelemetry_collector_contrib:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorOpentelemetry (39d78cb4-5c3d-536d-a86d-5fcb2abd36d8)
ProductOpentelemetry Collector Contrib (bf671b09-95af-51e2-b491-ee557fd433e4)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/open-telemetry/opentelemetry-collector-contrib purl2cpe 2026-06-01 10:13:47.656995
pkg:golang/github.com/open-telemetry/opentelemetry-collector-contrib purl2cpe 2026-06-01 10:13:47.656998

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2024-42368 vulnerable 2026-06-03 14:56:36.231647 open-telemetry has an Observable Timing Discrepancy
MEDIUM (6.5)
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
Published: 2024-08-13T19:31:16.814Z
Updated: 2024-08-14T13:38:51.917Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.