OpenTelemetry eBPF Instrumentation vulnerabilities

OpenTelemetry eBPF Instrumentation has a flaw that allows a local attacker controlling a Java workload to overwrite arbitrary host files. This issue exists in versions from 0.4.0 to before 0.8.0 when Java injection is enabled and OBI is running with elevated privileges.

In OpenTelemetry eBPF Instrumentation versions 0.7.0 to 0.8.9, a remotely reachable integer overflow in the memcached text protocol parser can crash the OBI process and cause denial of service.

In OpenTelemetry eBPF Instrumentation versions 0.1.0 to before 0.9.0, malformed MongoDB wire messages can trigger uncaught panics in the MongoDB TCP parser, allowing a remote unauthenticated attacker to crash the telemetry agent and cause a denial of service.

OpenTelemetry eBPF Instrumentation from version 0.7.0 to before version 0.9.0 mishandles writev buffers by reading only the first iovec entry but using the total iov_iter.count as the copy length. When log injection is enabled, a crafted multi-segment writev call can make OBI read and overwrite memory beyond the first segment.

OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. Prior to version 0.9.0, the Java TLS ioctl probe reads user-controlled ioctl pointers with bpf_probe_read instead of bpf_probe_read_user. An instrumented local process can therefore point OBI at kernel memory and cause that memory to be copied into telemetry.

OpenTelemetry eBPF Instrumentation prior to version 0.9.0 has a vulnerability in the custom CappedConcurrentHashMap used for Java TLS state tracking, which never removes keys from its insertion-order queue when entries are deleted, leading to heap memory exhaustion in long-running JVMs.

OpenTelemetry eBPF Instrumentation prior to version 0.9.0 has a vulnerability in the per-CPU message-buffer fallback path. It uses a 256-byte backup buffer but preserves the original payload size (up to 8KB). If a CPU mismatch occurs, OBI can read beyond the fallback buffer and leak adjacent memory into telemetry.

OpenTelemetry eBPF Instrumentation (OBI) before version 0.9.0 has a performance issue when replaying BPF probe hits into histogram observations. On busy systems, large run-count deltas cause excessive CPU usage by the metrics exporter.

OpenTelemetry eBPF Instrumentation (OBI) prior to version 0.9.0 exports raw Redis error text as the span status message. Since Redis error replies can contain attacker-controlled or sensitive values, this can lead to exfiltration of tokens, PII, or other confidential data into telemetry backends and injection of untrusted text into downstream analysis systems.

OpenTelemetry eBPF Instrumentation before version 0.9.0 has a bug in the Postgres protocol parser that assumes BIND message payloads contain a valid NUL-terminated portal name. A crafted empty or unterminated payload can cause OBI to slice beyond the buffer end and panic.

OpenTelemetry eBPF Instrumentation (OBI) prior to version 0.9.0 has a vulnerability in the ELF parser that trusts section offsets and counts from the executable file. A crafted local ELF file can cause the agent to panic while determining the process language.