CVE-2023-47108: DoS vulnerability in otelgrpc (uncontrolled resource consumption) due to unbound cardinality metrics
Noroxi assessment
Priority: Monitor (action score 31/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 2% (FIRST EPSS); higher than 81% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc (Go) 0.46.0; etcd (openSUSE:Leap 15.5) 3.5.12-150000.7.6.1; etcd (openSUSE:Leap 15.6) 3.5.12-bp156.4.3.1.
Low priority for now. Upgrade to go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc (Go) 0.46.0; etcd (openSUSE:Leap 15.5) 3.5.12-150000.7.6.1; etcd (openSUSE:Leap 15.6) 3.5.12-bp156.4.3.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Starting in version 0.37.0 and prior to version 0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion when many malicious requests are sent. An attacker can easily flood the peer address and port for requests. Version 0.46.0 contains a fix for this issue. 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`.
- BDU:2024-06663
- GHSA-8pgv-569h-w5rw
- GO-2023-2331
- openSUSE-SU-2024:13615-1
- openSUSE-SU-2024:13834-1
- openSUSE-SU-2024:13835-1
- openSUSE-SU-2024:13836-1
- openSUSE-SU-2024:14032-1
- openSUSE-SU-2024:14320-1
- openSUSE-SU-2024:14321-1
- openSUSE-SU-2025:0003-1
- RHSA-2024:0207
- RHSA-2024:0288
- RHSA-2024:0489
- SUSE-SU-2024:3188-1
- SUSE-SU-2024:3221-1
- SUSE-SU-2024:3656-1
- SUSE-SU-2024:4319-1
- SUSE-SU-2024:4360-1
- SUSE-SU-2025:20091-1
- Published
- Nov 10, 2023
- Updated
- Jun 17, 2026
- EPSS
- 2.0% · 81th percentile
- CWE
- CWE-770
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · GitHub_M
- 7.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| opentelemetry | opentelemetry | cpe:2.3:a:opentelemetry:opentelemetry |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- opentelemetry opentelemetrybefore 0.46.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
open-telemetry opentelemetry-go-contrib
- >= 0.37.0, < 0.46.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc | from 0.37.0 · before 0.46.0 | 0.46.0 |
| openSUSE:Leap 15.5 | etcd | before 3.5.12-150000.7.6.1 | 3.5.12-150000.7.6.1 |
| openSUSE:Leap 15.6 | etcd | before 3.5.12-bp156.4.3.1 | 3.5.12-bp156.4.3.1 |
| openSUSE:Leap Micro 5.5 | containerd | before 1.7.21-150000.117.1 | 1.7.21-150000.117.1 |
| openSUSE:Leap Micro 5.5 | docker | before 26.1.5_ce-150000.212.1 | 26.1.5_ce-150000.212.1 |
| openSUSE:Tumbleweed | containerd | before 1.7.21-1.1 | 1.7.21-1.1 |
| openSUSE:Tumbleweed | docker | before 26.1.5_ce-2.1 | 26.1.5_ce-2.1 |
| openSUSE:Tumbleweed | etcd | before 3.5.11-1.1 | 3.5.11-1.1 |
| openSUSE:Tumbleweed | etcd-for-k8s1.27 | before 3.5.12-1.1 | 3.5.12-1.1 |
| openSUSE:Tumbleweed | etcd-for-k8s1.28 | before 3.5.12-1.1 | 3.5.12-1.1 |
| openSUSE:Tumbleweed | etcd-for-k8s1.29 | before 3.5.12-1.1 | 3.5.12-1.1 |
| openSUSE:Tumbleweed | okteto | before 2.28.0-1.1 | 2.28.0-1.1 |
| Red Hat:openshift:4.12::el8 | cri-o | before 0:1.25.5-6.rhaos4.12.gitfcf6ef3.el8 | 0:1.25.5-6.rhaos4.12.gitfcf6ef3.el8 |
| Red Hat:openshift:4.12::el8 | cri-o-debuginfo | before 0:1.25.5-6.rhaos4.12.gitfcf6ef3.el8 | 0:1.25.5-6.rhaos4.12.gitfcf6ef3.el8 |
| Red Hat:openshift:4.12::el8 | cri-o-debugsource | before 0:1.25.5-6.rhaos4.12.gitfcf6ef3.el8 | 0:1.25.5-6.rhaos4.12.gitfcf6ef3.el8 |
| Red Hat:openshift:4.13::el8 | cri-o | before 0:1.26.4-9.1.rhaos4.13.gite26e057.el8 | 0:1.26.4-9.1.rhaos4.13.gite26e057.el8 |
| Red Hat:openshift:4.13::el8 | cri-o-debuginfo | before 0:1.26.4-9.1.rhaos4.13.gite26e057.el8 | 0:1.26.4-9.1.rhaos4.13.gite26e057.el8 |
| Red Hat:openshift:4.13::el8 | cri-o-debugsource | before 0:1.26.4-9.1.rhaos4.13.gite26e057.el8 | 0:1.26.4-9.1.rhaos4.13.gite26e057.el8 |
| Red Hat:openshift:4.13::el9 | cri-o | before 0:1.26.4-9.1.rhaos4.13.gite26e057.el9 | 0:1.26.4-9.1.rhaos4.13.gite26e057.el9 |
| Red Hat:openshift:4.13::el9 | cri-o-debuginfo | before 0:1.26.4-9.1.rhaos4.13.gite26e057.el9 | 0:1.26.4-9.1.rhaos4.13.gite26e057.el9 |
| Red Hat:openshift:4.13::el9 | cri-o-debugsource | before 0:1.26.4-9.1.rhaos4.13.gite26e057.el9 | 0:1.26.4-9.1.rhaos4.13.gite26e057.el9 |
| Red Hat:openshift:4.14::el8 | cri-o | before 0:1.27.2-7.rhaos4.14.git1cc7a64.el8 | 0:1.27.2-7.rhaos4.14.git1cc7a64.el8 |
| Red Hat:openshift:4.14::el8 | cri-o-debuginfo | before 0:1.27.2-7.rhaos4.14.git1cc7a64.el8 | 0:1.27.2-7.rhaos4.14.git1cc7a64.el8 |
| Red Hat:openshift:4.14::el8 | cri-o-debugsource | before 0:1.27.2-7.rhaos4.14.git1cc7a64.el8 | 0:1.27.2-7.rhaos4.14.git1cc7a64.el8 |
+12
Same product
opentelemetry: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-29181OpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)30Monitor
- CVE-2023-45142OpenTelemetry-Go Contrib has DoS vulnerability in otelhttp due to unbound cardinality metrics30Monitor
- CVE-2023-43810opentelemetry-instrumentation Denial of Service vulnerability due to unbound cardinality metrics30Monitor
Published before and after this one in the same product
- Later →CVE-2026-24051Feb 2, 2026 · OpenTelemetry-Go Affected by Arbitrary Code Execution via PATH Hijacking28Monitor
- Later →CVE-2026-39882Apr 8, 2026 · OpenTelemetry-Go OTLP HTTP exporters read unbounded HTTP response bodies21Monitor
- Later →CVE-2026-39883Apr 8, 2026 · OpenTelemetry-Go has an incomplete fix for CVE-2026-24051: BSD kenv command not using absolute path enables PATH hijacking29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc | 0.46.0 | Package registry (OSV) |
| opensuse:containerd | 1.7.21-150000.117.1 · openSUSE:Leap Micro 5.5 | Package registry (OSV) |
| opensuse:docker | 26.1.5_ce-150000.212.1 · openSUSE:Leap Micro 5.5 | Package registry (OSV) |
| opensuse:etcd | 3.5.12-150000.7.6.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:etcd | 3.5.12-bp156.4.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:etcd-for-k8s1.27 | 3.5.12-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:etcd-for-k8s1.28 | 3.5.12-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:etcd-for-k8s1.29 | 3.5.12-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:okteto | 2.28.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:cri-o | 0:1.27.2-7.rhaos4.14.git1cc7a64.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| red hat:cri-o-debuginfo | 0:1.27.2-7.rhaos4.14.git1cc7a64.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| red hat:cri-o-debugsource | 0:1.27.2-7.rhaos4.14.git1cc7a64.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| suse:containerd | 1.7.21-150000.117.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:containerd | 1.7.21-16.94.1 · SUSE:Linux Enterprise Module for Containers 12 | Package registry (OSV) |
| suse:docker | 26.1.5_ce-150000.212.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:docker | 26.1.5_ce-98.120.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:docker-compose | 2.33.1-1.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:etcd | 3.5.12-bp156.4.3.1 · SUSE:Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2024-06-25 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+227 d
- TodayNov 8, 2026+1093 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-4514229 days apartOpenTelemetry-Go Contrib has DoS vulnerability in otelhttp due to unbound cardinality metrics30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- github.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
- github.com/open-telemetry/opentelemetry-go-contrib/commit/04c5dcbb5b35f14b4e6793b245919c72addbc7d0
- github.com/open-telemetry/opentelemetry-go-contrib/commit/b44dfc9092b157625a5815cb437583cee663333b
- github.com/open-telemetry/opentelemetry-go-contrib/pull/4322
- github.com/open-telemetry/opentelemetry-go-contrib/security/advisories/GHSA-8pgv-569h-w5rw
- pkg.go.dev/go.opentelemetry.io/otel/metric/noop#NewMeterProvider
Vendor advisories and official records. Exploit/PoC links are deliberately left out.