Skip to content

← Public intelligence

Go package

go.opentelemetry.io/contrib/instrumentation/github.com/astaxie/beego/otelbeego

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5GoPublished

    otelhttp and otelbeego have DoS vulnerability for high cardinality metrics

    CVE-2023-25151 · GHSA-5r5m-65gx-7vrh

    Affected
    • Go go.opentelemetry.io/contrib/instrumentation/github.com/astaxie/beego/otelbeego >= 0.38.0, < 0.39.0
    Fixed in
    0.39.0· Vendor fix available
    Issue
    Impact The v0.38.0 release of go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp uses the httpconv.ServerRequest function to annotate metric measurements for the http.server.requestcontentlength, http.server.responsecontentlength, and http.server.duration instruments. The ServerRequest function sets the http.target attribute value to be the whole request URI (including the query string)[^1]. The metric instruments do not "forget" previous measurement attributes when cumulative temporality is used, this means the cardinality of the measurements allocated is directly correlated with the unique URIs handled. If the query string is constantly random, this will result in a constant increase in memory allocation that can be used in a denial-of-service attack. Pseudo-attack: Patches - go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp - v0.39.0 - go.opentelemetry.io/contrib/instrumentation/github.com/astaxie/beego/otelbeego - v0.39.0 [^1]:…

    Recommended action: Upgrade to 0.39.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →