Unbounded HTTP response body read in OpenTelemetry.Sampler.AWS
open-telemetry opentelemetry-dotnet-contrib
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| OpenTelemetry.Sampler.AWS NuGet |
|
|
| OpenTelemetry.Resources.AWS NuGet |
|
|
open-telemetry opentelemetry-dotnet-contrib
| Product | Affected | Fixed in |
|---|---|---|
| OpenTelemetry.Sampler.AWS NuGet |
|
|
| OpenTelemetry.Resources.AWS NuGet |
|
|
The AWS X-Ray Remote Sampler package provides a sampler which can get sampling configurations from AWS X-Ray. Prior to 0.1.0-alpha.8, OpenTelemetry.Sampler.AWS reads unbounded HTTP response bodies from a configured AWS X-Ray remote sampling endpoint into memory. AWSXRaySamplerClient.DoRequestAsync called HttpClient.SendAsync followed by ReadAsStringAsync(), which materializes the entire HTTP response body into a single in-memory string with no size limit. The sampling endpoint is configurable via AWSXRayRemoteSamplerBuilder.SetEndpoint (default: http://localhost:2000). An attacker who controls the configured endpoint, or who can intercept traffic to it (MitM), can return an arbitrarily large response body. This causes unbounded heap allocation in the consuming process, leading to high transient memory pressure, garbage-collection stalls, or an OutOfMemoryException that terminates the process. This vulnerability is fixed in 0.1.0-alpha.8.
From the CVE record · GitHub_M
OpenTelemetry.Sampler.AWS reads responses from its configured AWS X-Ray remote sampling endpoint into memory without a size limit. An attacker who controls that endpoint or can intercept its traffic can return a large response that causes memory pressure, garbage-collection stalls, or process termination.
Engineers using NuGet OpenTelemetry.Sampler.AWS versions before 0.1.0-alpha.8 or OpenTelemetry.Resources.AWS versions before 1.15.1 should check their deployments.