CVE-2023-45142: OpenTelemetry-Go Contrib has DoS vulnerability in otelhttp due to unbound cardinality metrics

Published Oct 12, 2023
·
Updated

Summary

This handler wrapper https://github.com/open-telemetry/opentelemetry-go-contrib/blob/5f7e6ad5a49b45df45f61a1deb29d7f1158032df/instrumentation/net/http/otelhttp/handler.go#L63-L65 out of the box adds labels

- http.useragent - http.method

that have unbound cardinality. It leads to the server's potential memory exhaustion when many malicious requests are sent to it.

Details

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.

PoC

Send many requests with long randomly generated HTTP methods or/and User agents (e.g. a million) and observe how memory consumption increases during it.

Impact

In order to be affected, the program has to configure a metrics pipeline, use otelhttp.NewHandler wrapper, and does not filter any unknown HTTP methods or User agents on the level of CDN, LB, previous middleware, etc.

Others

It is similar to already reported vulnerabilities - https://github.com/open-telemetry/opentelemetry-go-contrib/security/advisories/GHSA-5r5m-65gx-7vrh (open-telemetry/opentelemetry-go-contrib) - https://github.com/advisories/GHSA-cg3q-j54f-5p7p (prometheus/clientgolang)

Workaround for affected versions

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 mark 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 behavior, library API should allow to enable it.

The other possibility is to disable HTTP metrics instrumentation by passing otelhttp.WithMeterProvider option with noop.NewMeterProvider.

Solution provided by upgrading

In PR https://github.com/open-telemetry/opentelemetry-go-contrib/pull/4277, released with package version 0.44.0, 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.

References

- https://github.com/open-telemetry/opentelemetry-go-contrib/pull/4277 - https://github.com/open-telemetry/opentelemetry-go-contrib/releases/tag/v1.19.0

Other sources

OpenTelemetry-Go Contrib has DoS vulnerability in otelhttp due to unbound cardinality metrics

Microsoft

OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. A handler wrapper out of the box adds labels http.useragent and http.method that have unbound cardinality. 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. In order 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. Version 0.44.0 fixed this issue 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 mark 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 behavior, library API should allow to enable it.

MITRE

Affected Software

28 affected componentsFixes available
go/go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace<0.44.0
0.44.0
go/go.opentelemetry.io/contrib/instrumentation/gopkg.in/macaron.v1/otelmacaron<0.44.0
0.44.0
go/go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho<0.44.0
0.44.0
go/go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux<0.44.0
0.44.0
go/go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin<0.44.0
0.44.0
go/go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful<0.44.0
0.44.0
go/go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp<0.44.0
0.44.0
OpenTelemetry OpenTelemetry Go<0.44.0
redhat/opentelemetry-go<0.44.0
0.44.0
Microsoft azl3 prometheus-adapter 0.11.2-1
Microsoft azl3 cert-manager 1.12.12-1
Microsoft azl3 kubernetes 1.29.1-2
Microsoft azl3 prometheus 2.45.4-1
Microsoft azl3 opa 0.63.0-1
Microsoft azl3 prometheus-adapter 0.12.0-1
Microsoft azl3 kube-vip-cloud-provider 0.0.10-1
Microsoft azl3 docker-buildx 0.14.0-1
Microsoft azl3 kube-vip-cloud-provider 0.0.7-1
Microsoft azl3 opa 0.55.0-1
Microsoft cbl2 cri-tools 1.29.0-2
Microsoft cbl2 moby-compose 2.17.3-7
Microsoft azl3 docker-buildx 0.12.1-1
Microsoft cbl2 opa 0.63.0-1
Microsoft cbl2 moby-engine 24.0.9-10
Microsoft azl3 prometheus 2.37.0-11
Microsoft azl3 kubernetes 1.28.7-2
Microsoft cbl2 opa 0.50.2-8
Microsoft azl3 cert-manager 1.11.2-8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace to a version that resolves this vulnerability.

    Fixed in 0.44.0
  2. Upgrade

    Upgrade go/go.opentelemetry.io/contrib/instrumentation/gopkg.in/macaron.v1/otelmacaron to a version that resolves this vulnerability.

    Fixed in 0.44.0
  3. Upgrade

    Upgrade go/go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho to a version that resolves this vulnerability.

    Fixed in 0.44.0
  4. Upgrade

    Upgrade go/go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux to a version that resolves this vulnerability.

    Fixed in 0.44.0
  5. Upgrade

    Upgrade go/go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin to a version that resolves this vulnerability.

    Fixed in 0.44.0
  6. Upgrade

    Upgrade go/go.opentelemetry.io/contrib/instrumentation/github.com/emicklei/go-restful/otelrestful to a version that resolves this vulnerability.

    Fixed in 0.44.0
  7. Upgrade

    Upgrade go/go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp to a version that resolves this vulnerability.

    Fixed in 0.44.0
  8. Upgrade

    Upgrade redhat/opentelemetry-go to a version that resolves this vulnerability.

    Fixed in 0.44.0
  9. Configuration

    Use otelhttp.WithFilter() to prevent recording metrics for requests with untrusted or high-cardinality HTTP methods and User-Agent headers; carefully configure the filter to avoid dropping legitimate traffic entirely.

    go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp WithFilter = apply filter to exclude or ignore requests with non-standard/high-cardinality http.method and http.user_agent values
  10. Configuration

    Disable HTTP metrics instrumentation by passing otelhttp.WithMeterProvider(noop.NewMeterProvider()) so no high-cardinality HTTP metrics are produced.

    go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp WithMeterProvider = noop.NewMeterProvider
  11. Compensating control

    Filter or normalize HTTP methods and User-Agent headers at the CDN, load balancer, WAF, or ingress (e.g., block or map non-standard/random methods and long/unknown User-Agent values, enforce rate limits) to prevent unbounded metric cardinality prior to the application.

Event History

Oct 12, 2023
CVE Published
via MITRE·04:33 PM
Data Sourced
via MITRE·04:33 PM
DescriptionSeverityWeakness
Oct 16, 2023
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Advisory Published
via GitHub·02:01 PM
Oct 19, 2023
Data Sourced
via Red Hat·10:13 PM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2023-45142?

CVE-2023-45142 is a vulnerability in OpenTelemetry-Go Contrib that has a high severity rating of 7.5.

2

What is the impact of CVE-2023-45142?

CVE-2023-45142 allows an attacker to cause a denial-of-service (DoS) or potentially execute arbitrary code.

3

Which versions of OpenTelemetry-Go Contrib are affected by CVE-2023-45142?

OpenTelemetry-Go Contrib versions up to (but not including) 0.44.0 are affected by CVE-2023-45142.

4

How do I fix CVE-2023-45142?

To fix CVE-2023-45142, update to OpenTelemetry-Go Contrib version 0.44.0 or later.

5

Where can I find more information about CVE-2023-45142?

You can find more information about CVE-2023-45142 in the GitHub security advisory and the OpenTelemetry-Go Contrib GitHub repository.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203