Allocation of Resources Without Limits or Throttling in github.com/open-telemetry/opentelemetry-go-contrib
CVE-2023-45142
- github.com/open-telemetry/opentelemetry-go-contrib
- go.opentelemetry.io/contrib
- go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful
- go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin
- go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux
- go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho
- go.opentelemetry.io/contrib/instrumentation/gopkg.in/macaron.v1/otelmacaron
- go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace
- go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp
- open-telemetry/opentelemetry-go-contrib
Summary
OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. A handler wrapper out of the box adds labels `http.user_agent` and `http.method` that have unbound cardinality. In versions through 0.43.0, and 1.0.0 through 1.18.0, it leads to the server's potential memory exhaustion when many malicious requests are sent to it. HTTP header User-Agent or HTTP method for requests can be easily set by an attacker to be random and long. The library internally uses `httpconv.ServerRequest` that records every value for HTTP `method` and `User-Agent`. To be affected, a program has to use the `otelhttp.NewHandler` wrapper and not filter any unknown HTTP methods or User agents on the level of CDN, LB, previous middleware, etc. This issue was fixed when the values collected for attribute `http.request.method` were changed to be restricted to a set of well-known values and other high cardinality attributes were removed. As a workaround to stop being affected, `otelhttp.WithFilter()` can be used, but it requires manual careful configuration to not log certain requests entirely. For convenience and safe usage of this library, it should by default be marked with the label `unknown` non-standard HTTP methods and User agents to show that such requests were made but do not increase cardinality. In case someone wants to stay with the current behaviour, library API should allow to enable it.
- LOW
- NETWORK
- NONE
- UNCHANGED
- NONE
- NONE
- NONE
- HIGH
CWE-770 - Allocation of Resources Without Limits or Throttling
The software allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.
References
Advisory Timeline
- Published