CyberRota Analysis
AI-GeneratedOpenTelemetry-Go versions 1.5.0 to 1.44.0 are vulnerable due to the internal logging of sensitive configuration details, including collector endpoints and potentially embedded credentials in Zipkin URLs, when the Info-level logging is enabled. This could allow unauthorized access to internal collector topology and sensitive information for applications that utilize otel.SetLogger for logging. Organizations using affected versions should prioritize upgrading to version 1.45.0 to mitigate the risk of exposing sensitive data through logs.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.5.0 to 1.44.0, sdk/trace.NewTracerProvider emits a TracerProvider created internal Info-level diagnostic event whose MarshalLog implementations recursively include span processor, exporter, and client configuration. Applications that call otel.SetLogger to enable OpenTelemetry internal Info logging can therefore record OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure flag, and complete Zipkin collector URLs. A person or system with access to those logs can learn internal collector topology and can recover credentials or tokens embedded in Zipkin URL user information or query strings. The default OpenTelemetry logger does not emit the event, and this path does not log OTLP authentication headers, TLS key material, or span payloads. This issue is fixed in version 1.45.0.