Bump xk6 OTLP trace exporters to OpenTelemetry-Go 1.45.0

[Copilot]

Tl;dr: Remove vulnerable OpenTelemetry-Go OTLP trace exporter versions from long-running-test-arch/xk6 by pinning the transitive trace modules to v1.45.0.

Context:

Dependabot flagged go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.43.0 for exporter config logging that can leak collector endpoints when verbose internal OpenTelemetry logging is enabled. This change updates the xk6 module’s transitive OTLP trace exporter set to the lowest patched version and keeps the scope limited to Go dependency metadata.

• Dependency update

  • go.opentelemetry.io/otel/exporters/otlp/otlptrace → v1.45.0
  • go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc → v1.45.0
  • go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp → v1.45.0

• Reachability assessment

  • long-running-test-arch/xk6/k6_otel.go uses only OTLP metric export (otlpmetricgrpc) and metric.NewMeterProvider
  • repo search found no uses of otel.SetLogger, sdktrace.NewTracerProvider, zipkin, or otlptracehttp
  • go mod why -m shows the vulnerable trace exporters are present only transitively via go.k6.io/k6/.../internal/lib/trace
  • Conclusion: the advisory path is not reachable from this repository’s own xk6 extension code; this is primarily a dependency-graph remediation
  • Confidence: high

• Resulting module state

require (
    go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.45.0 // indirect
    go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.45.0 // indirect
    go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.45.0 // indirect
)

Test Plan:

• cd long-running-test-arch/xk6 && go test ./...
• verify resolved OTLP trace exporter modules are v1.45.0

Test services data

1. e-1712644058766987264
2. e-1712643928659124224
3. e-1742334541200846848
4. e-1777406072376840192

Original prompt

---

This section details the Dependabot vulnerability alert you should resolve

<alert_title>OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs</alert_title>
<alert_description>### Summary

OpenTelemetry Go versions 1.5.0 through 1.44.0 can include trace exporter endpoint configuration in an internal diagnostic log emitted when an SDK TracerProvider is created. The default OpenTelemetry logger does not emit this event. Exposure requires an application to install a logger that enables OpenTelemetry's internal Info-level diagnostics and for someone other than the intended audience to have access to those logs.

The logged configuration can disclose the address of the trace collector and whether the OTLP/HTTP connection is configured as insecure. The Zipkin exporter logs its complete collector URL, so credentials in URL userinfo or tokens in the query string are also disclosed if an application embeds them there. OTLP authentication headers, TLS key material, and exported span data are not included in this log.

Exporter MarshalLog implementations that caused this configuration to be included in internal logs were introduced by a1fff3c.

Details

When sdk/trace.NewTracerProvider constructs a provider, it records a TracerProvider created internal Info event containing the provider configuration. In affected versions, the configuration's MarshalLog methods recursively include:

1. the provider's span processors;
2. each processor's span exporter; and
3. for the OTLP trace exporter, its client configuration.

This causes the following values to be present in the event:

• OTLP trace gRPC: the configured endpoint;
• OTLP trace HTTP: the configured endpoint and the Insecure flag; and
• Zipkin: the complete collector URL.

OpenTelemetry Go does not emit this event with its default logger, which only emits errors. An application must explicitly configure a sufficiently verbose logger with otel.SetLogger. The required logr verbosity is version-dependent:

• versions 1.5.0 through 1.14.x use V(1) for this Info event; and
• versions 1.15.0 through 1.44.0 use V(4).

OTLP header configuration is not part of the marshaled object, so credentials supplied with WithHeaders or the corresponding environment variables are not exposed. The documented OTLP WithEndpoint input is a collector address rather than a credential-bearing URL. The higher-risk case is therefore the Zipkin collector URL, which is retained and logged in full, or an application passing sensitive data in an OTLP endpoint outside the documented format.

Proof of concept

The following program demonstrates the behavior with OpenTelemetry Go 1.44.0. It deliberately places credentials and a token in the Zipkin collector URL and enables internal Info logging:

package main

import (
	"bytes"
	"context"
	"fmt"

	"github.com/go-logr/logr/funcr"
	"go.opentelemetry.io/otel"
	"go.opentelemetry.io/otel/exporters/zipkin"
	sdktrace "go.opentelemetry.io/otel/sdk/trace"
)

func main() {
	var logs bytes.Buffer
	otel.SetLogger(funcr.New(func(_, args string) {
		_, _ = logs.WriteString(args)
	}, funcr.Options{Verbosity: 4}))

	exporter, err := zipkin.New(
		"http://user:pass@zipkin.internal:9411/api/v2/spans?token=secret",
	)
	if err != nil {
		panic(err)
	}

	tp := sdktrace.NewTracerProvider(sdktrace.WithBatcher(exporter))
	_ = tp.Shutdown(context.Background())

	fmt.Println(logs.String())
}

The TracerProvider created event contains:

http://user:pass@zipkin.internal:9411/api/v2/spans?token=secret

For versions before 1.15.0, set funcr.Options{Verbosity: 1} instead.

Impact

This is a conditional disclosure through application logs. Affected applications must enable verbose OpenTelemetry internal diagnostics and configure a trace exporter containing information they do not intend to expose to readers of those logs. In that configuration, a person or system with log access can learn the trace collector address and internal network topology. If credentials or tokens are embedded directly in a Zipkin collector URL, those values can also be recovered from the logs.

There is no exposure with the default OpenTelemetry logger, and the vulnerable log is generated from local application configuration rather than remotely supplied span data. OTLP authentication headers, certificate or private-key contents, and telemetry payloads are not logged by this path.

Remediation

Upgrade the affected OpenTelemetry Go modules to version 1.45.0 or later. The fix in 3a1412d stops recursively marshaling exporter and client configuration and records their types instead.

If an immediate upgrade is not possible:

• keep OpenTelemetry internal logging below the Info verbosity described above;
• do ...

• Resolves solarwinds/apm-java alert NH2669: Dependencies: Upgrade Otel agent to 1.7.2 #16

[cleverchuk]

@copilot resolve conflict

[Copilot]

@copilot resolve conflict

Resolved in 088cde5 by merging main into this branch and fixing the long-running-test-arch/xk6/go.sum conflict.