Описание
Swift W3C TraceContext vulnerable to a malformed HTTP header causing a crash
Impact
A denial-of-service vulnerability due to improper input validation allows a remote attacker to crash the service via a malformed HTTP header.
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.
Patches
Workarounds
Disable either Swift OTel or the code that extracts the trace information from an incoming header (such as a TracingMiddleware).
References
Ссылки
- https://github.com/swift-otel/swift-w3c-trace-context/security/advisories/GHSA-mvpq-2v8x-ww6g
- https://nvd.nist.gov/vuln/detail/CVE-2026-23886
- https://github.com/swift-otel/swift-w3c-trace-context/commit/5da9b143ba6046734de3fa51dafea28290174e4e
- https://github.com/swift-otel/swift-otel/releases/tag/1.0.4
- https://github.com/swift-otel/swift-w3c-trace-context/releases/tag/1.0.0-beta.5
Пакеты
github.com/swift-otel/swift-w3c-trace-context
< 1.0.0-beta.5
1.0.0-beta.5
github.com/swift-otel/swift-otel
< 1.0.4
1.0.4
Связанные уязвимости
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`).