otelgrpc DoS vulnerability due to unbound cardinality metrics
Published 12 Nov 2023 · Updated 10 Sept 2026
Is your project on an affected go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=0.37.0 <0.46.0
- Fixed in
- 0.46.0
go get go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc@v0.46.0Details
Summary
The grpc Unary Server Interceptor opentelemetry-go-contrib/instrumentation/google.golang.org/grpc/otelgrpc/interceptor.go
// UnaryServerInterceptor returns a grpc.UnaryServerInterceptor suitable
// for use in a grpc.NewServer call.
func UnaryServerInterceptor(opts ...Option) grpc.UnaryServerInterceptor {out of the box adds labels
net.peer.sock.addrnet.peer.sock.port
that have unbound cardinality. It leads to the server's potential memory exhaustion when many malicious requests are sent.
Details
An attacker can easily flood the peer address and port for requests.
PoC
Apply the attached patch to the example and run the client multiple times. Observe how each request will create a unique histogram and how the memory consumption increases during it.
Impact
In order to be affected, the program has to configure a metrics pipeline, use UnaryServerInterceptor, and does not filter any client IP address and ports via middleware or proxies, etc.
Others
It is similar to already reported vulnerabilities.
- GHSA-rcjv-mgp8-qvmr (open-telemetry/opentelemetry-go-contrib)
- [GHSA-5r5m-65gx-7vrh](https://github.com/open-telemetry/opentelemetry-go-contrib/security/advisories/GHSA-5r5m-65gx-7vrh "GHSA-5r5m-65gx-7vrh") (open-telemetry/opentelemetry-go-contrib)
- [GHSA-cg3q-j54f-5p7p](https://github.com/advisories/GHSA-cg3q-j54f-5p7p "GHSA-cg3q-j54f-5p7p") (prometheus/client_golang)
Workaround for affected versions
As a workaround to stop being affected, a view removing the attributes can be used.
The other possibility is to disable grpc metrics instrumentation by passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`.
Solution provided by upgrading
In PR #4322, to be released with v0.46.0, the attributes were removed.
References
Is GHSA-8pgv-569h-w5rw in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc, and gives you the command that fixes it.
References
- Linkgithub.com/open-telemetry/opentelemetry-go-contrib/security/advisories/GHSA-8pgv-569h-w5rw
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-47108
- Linkgithub.com/open-telemetry/opentelemetry-go-contrib/pull/4322
- Linkgithub.com/open-telemetry/opentelemetry-go-contrib/commit/04c5dcbb5b35f14b4e6793b245919c72addbc7d0
- Linkgithub.com/open-telemetry/opentelemetry-go-contrib/commit/b44dfc9092b157625a5815cb437583cee663333b
- Packagegithub.com/open-telemetry/opentelemetry-go-contrib
- Linkgithub.com/open-telemetry/opentelemetry-go-contrib/blob/9d4eb7e7706038b07d33f83f76afbe13f53d171d/instrumentation/google.golang.org/grpc/otelgrpc/interceptor.go#L327
- Linkgithub.com/open-telemetry/opentelemetry-go-contrib/blob/instrumentation/google.golang.org/grpc/otelgrpc/v0.45.0/instrumentation/google.golang.org/grpc/otelgrpc/config.go#L138
- Linkpkg.go.dev/go.opentelemetry.io/otel/metric/noop#NewMeterProvider
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.