Swift W3C TraceContext has malformed HTTP header that can cause a crash
swift-otel swift-w3c-trace-context
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/swift-otel/swift-w3c-trace-context Swift |
|
|
| github.com/swift-otel/swift-otel Swift |
|
|
swift-otel swift-w3c-trace-context
| Product | Affected | Fixed in |
|---|---|---|
| github.com/swift-otel/swift-w3c-trace-context Swift |
|
|
| github.com/swift-otel/swift-otel Swift |
|
|
Swift W3C TraceContext is a Swift implementation of the W3C Trace Context standard, and Swift OTel is an OpenTelemetry Protocol (OTLP) backend for Swift Log, Swift Metrics, and Swift Distributed Tracing. Prior to Swift W3C TraceContext version 1.0.0-beta.5 and Swift OTel version 1.0.4, a denial-of-service vulnerability due to improper input validation allows a remote attacker to crash the service via a malformed HTTP header. This allows crashing the process with data coming from the network when used with, for example, an HTTP server. Most common way of using Swift W3C Trace Context is through Swift OTel. Version 1.0.0-beta.5 of Swift W3C TraceContext and version 1.0.4 of Swift OTel contain a patch for this issue. As a workaround, disable either Swift OTel or the code that extracts the trace information from an incoming header (such as a `TracingMiddleware`).
From the CVE record · GitHub_M
Improper input validation in Swift W3C TraceContext and Swift OTel can crash a service when it processes a malformed HTTP header. A remote attacker can trigger the crash with network-supplied data when trace information is extracted from incoming headers, such as in an HTTP server; no user interaction is described.
Check services using swift-w3c-trace-context before 1.0.0-beta.5 or swift-otel before 1.0.4.