OpenTelemetry.Exporter.OpenTelemetryProtocol
Affected
- introduced
1.8.0, fixed1.15.3(ecosystem)
Fixed versions
1.15.3
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-42191
OpenTelemetry's disk retry default temp path enables local blob injection via OTLP Exporter
Summary
The OTLP disk retry feature in OpenTelemetry.Exporter.OpenTelemetryProtocol silently fell back to Path.GetTempPath() when OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=disk was set but OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATH was not configured.
The exporter stored and loaded *.blob files under fixed, signal-named subdirectories (traces, metrics, logs) beneath that shared temporary root path.
On multi-user systems where the temporary directory is accessible to other local accounts, this exposed three attack surfaces:
*.blob files into the predictable path; the exporter picks them up on the next retry cycle and forwards them to the configured OTLP endpoint under the application's identity.*.blob files written by the application between export failures, recovering encoded telemetry payloads (spans, metric data points, log records).Details
Preconditions
OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY is set to disk.OTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_DIRECTORY_PATH is not set, causing the exporter to resolve the blob storage root using the System.IO.Path.GetTempPath() API./tmp on Linux, or %TEMP% on a multi-user Windows installation).Exploit path
OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY=disk and no explicit blob directory. The exporter resolves the storage root to Path.GetTempPath(), producing paths such as %TEMP%\traces, %TEMP%\metrics, and %TEMP%\logs (or /tmp/traces etc. on Linux).*.blob files into one of those signal subdirectories. On the next retry interval (by default every 60 seconds), `OtlpExporterPersistentStorageTransmissionHandler` scans the directory, loads the attacker-supplied blobs, and forwards them to the configured OTLP endpoint using the application's identity and transport credentials.*.blob files that the application wrote after a transient export failure, recovering the full serialized telemetry payloads (spans, metric data points, or log records in Protobuf encoding).Mitigations
If an immediate upgrade to a patched version is not possible:
*.blob files or abnormal retry backlog growth.Resources
Medium Basis: The source's own band: MODERATE
1.8.0, fixed 1.15.3 (ecosystem)1.15.3
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0