OpenTelemetry.Exporter.OneCollector vulnerable to denial of service via unbounded HTTP error response body
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| open-telemetry | opentelemetry-dotnet-contrib | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Opentelemetry | Opentelemetry-dotnet-contrib |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-55m9-299j-53c7 | OneCollector exporter reads unbounded HTTP response bodies |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.338% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opentelemetry opentelemetry.exporter.onecollector
|
|
| CPEs | cpe:2.3:a:opentelemetry:opentelemetry.exporter.onecollector:*:*:*:*:*:.net:*:* | |
| Vendors & Products |
Opentelemetry opentelemetry.exporter.onecollector
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opentelemetry
Opentelemetry opentelemetry-dotnet-contrib |
|
| Vendors & Products |
Opentelemetry
Opentelemetry opentelemetry-dotnet-contrib |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenTelemetry.Exporter.OneCollector is a .NET exporter that sends telemetry to a OneCollector back-end over HTTP. In versions 1.15.0 and earlier, when a request to the configured back-end or collector results in an unsuccessful HTTP 4xx or 5xx response, the HttpJsonPostTransport class reads the entire response body into memory with no upper bound on the number of bytes consumed in order to include the error response in operator logs. An attacker who controls the configured endpoint, or who can intercept traffic to it via a man-in-the-middle attack, 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. As a workaround, use network-level controls such as firewall rules, mTLS, or a service mesh to prevent man-in-the-middle attacks on the configured back-end or collector endpoint. This issue is fixed in version 1.15.1, which limits the number of bytes read from the response body in an error condition to 4 MiB. | |
| Title | OpenTelemetry.Exporter.OneCollector vulnerable to denial of service via unbounded HTTP error response body | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV3_1
|