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.
CVE-2023-47108
“—” beside the score: it is equal to NVD's CVSS score.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2023-11-12. NVD baseline CVSS 7.5; sources differ by 0.0.
Also known asEUVD-2023-2927 (ENISA EUVD) · GHSA-8pgv-569h-w5rw (GitHub Security Advisories) · GO-2023-2331 (OSV.dev)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 65EG Risk 65/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 2.0%
- EPSS %ILE
- 81st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 2.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 10, 2023
Last Modified
June 17, 2026
References (7)
- security-advisories@github · CVE Programhttps://github.com/open-telemetry/opentelemetry-go-contrib/blob/9d4eb7e7706038b07d33f83f76afbe13f53d171d/instrumentation/google.golang.org/grpc/otelgrpc/interceptor.go#L327Product
- security-advisories@github · CVE Programhttps://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#L138Product
- security-advisories@githubhttps://github.com/open-telemetry/opentelemetry-go-contrib/commit/04c5dcbb5b35f14b4e6793b245919c72addbc7d0
- security-advisories@github · CVE Programhttps://github.com/open-telemetry/opentelemetry-go-contrib/commit/b44dfc9092b157625a5815cb437583cee663333bPatch
- security-advisories@github · CVE Programhttps://github.com/open-telemetry/opentelemetry-go-contrib/pull/4322Issue Tracking · Patch
- security-advisories@github · CVE Programhttps://github.com/open-telemetry/opentelemetry-go-contrib/security/advisories/GHSA-8pgv-569h-w5rwVendor Advisory
- security-advisories@github · CVE Programhttps://pkg.go.dev/go.opentelemetry.io/otel/metric/noop#NewMeterProviderProduct
Vendor Advisories for CVE-2023-47108(20)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2023-47108Microsoft Security Response Center (MSRC)
CVE-2023-47108
- RHSA-2025:0029Red Hat Product SecurityMedium
Red Hat Security Advisory: OpenShift Container Platform 4.14.44 bug fix and security update
- RHSA-2024:11293Red Hat Product SecurityMedium
Red Hat Security Advisory: Multicluster Engine for Kubernetes 2.6.4 security enhancements and bug fixes
- RHSA-2024:10857Red Hat Product SecurityMedium
Red Hat Security Advisory: Multicluster Engine for Kubernetes 2.7.2 security updates and bug fixes
- RHSA-2024:8235Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.14.39 security update
- RHSA-2024:7184Red Hat Product SecurityMedium
Red Hat Security Advisory: OpenShift Container Platform 4.14.38 security update
- RHSA-2024:6811Red Hat Product SecurityHigh
Red Hat Security Advisory: OpenShift Container Platform 4.13.51 bug fix and security update
- RHSA-2024:6637Red Hat Product SecurityMedium
Red Hat Security Advisory: OpenShift Container Platform 4.15.32 bug fix and security update
- +12 more
Patch Availability(31)
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(14)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
- Red HatRHSA-2023:7197MODERATE2023-11-10
RHSA-2023:7197 — Moderate
- Red HatRHSA-2023:7198MODERATE2023-11-10
RHSA-2023:7198 — Moderate
- Red HatRHSA-2023:7681MODERATE2023-11-10
RHSA-2023:7681 — Moderate
- Red HatRHSA-2023:7831MODERATE2023-11-10
RHSA-2023:7831 — Moderate
- Red HatRHSA-2024:0204MODERATE2023-11-10
RHSA-2024:0204 — Moderate
- Red HatRHSA-2024:0207MODERATE2023-11-10
RHSA-2024:0207 — Moderate
- Red HatRHSA-2024:0288MODERATE2023-11-10
RHSA-2024:0288 — Moderate
- Red HatRHSA-2024:0489MODERATE2023-11-10
RHSA-2024:0489 — Moderate
- Red HatRHSA-2024:0642MODERATE2023-11-10
RHSA-2024:0642 — Moderate
- Red HatRHSA-2024:0741MODERATE2023-11-10
RHSA-2024:0741 — Moderate
- Red HatRHSA-2024:0766MODERATE2023-11-10
RHSA-2024:0766 — Moderate
- Red HatRHSA-2024:1328MODERATE2023-11-10
RHSA-2024:1328 — Moderate
- Red HatRHSA-2024:1449MODERATE2023-11-10
RHSA-2024:1449 — Moderate
- Red HatRHSA-2024:1458MODERATE2023-11-10
RHSA-2024:1458 — Moderate
Data Freshness Timeline
(refreshed 10× in last 7d / 39× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 94 of 209 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 115 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 08:18 UTCGHSA enrichmentGHSA-8pgv-569h-w5rw · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-01 08:18 UTCEG score recompute
- 2026-10-31 16:30 UTCEPSS rescoreEPSS 2.0% · 81st percentile
- 2026-10-30 16:31 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-29 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-28 20:29 UTCEG score recompute
- 2026-10-28 20:29 UTCVendor advisory
- 2026-10-28 19:25 UTCOSV refresh
- 2026-10-28 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-27 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-25 17:32 UTCEG score recompute
- 2026-10-25 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-24 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-23 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-22 16:31 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-21 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-20 21:57 UTCEG score recompute
- 2026-10-20 21:57 UTCVendor advisory
- 2026-10-20 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-19 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-18 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-18 07:47 UTCEG score recompute
- 2026-10-17 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-16 16:36 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-15 16:29 UTCEPSS rescoreEPSS 2.0% · 80th percentile
Show 69 moreShow fewer
- 2026-10-14 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-13 16:30 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-12 18:16 UTCEG score recompute
- 2026-10-12 16:54 UTCOSV refresh
- 2026-10-12 16:31 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-11 21:42 UTCEG score recompute
- 2026-10-11 13:45 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-10 19:57 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-09 20:05 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-08 17:06 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-07 23:46 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-06 15:15 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-05 17:41 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-30 16:33 UTCEG score recompute
- 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-28 13:49 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-22 16:58 UTCOSV refresh
- 2026-09-22 14:46 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-21 20:31 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-17 19:25 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-16 05:11 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-13 16:44 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-12 14:58 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-11 14:50 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-11 09:34 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-07 15:59 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-05 15:26 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-09-04 13:58 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.6% · 74th percentile
- 2026-09-03 13:16 UTCOSV refresh
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-09-01 04:35 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-30 19:15 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-30 01:20 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-26 14:44 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-24 14:14 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-23 00:17 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-20 22:53 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-17 13:45 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-17 02:48 UTCOSV refresh
- 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-16 02:12 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-15 01:28 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-13 21:58 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-12 13:49 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-11 13:40 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-10 23:57 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
- 2026-08-08 16:35 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2023:7197 · redhat:RHSA-2023:7198 · redhat:RHSA-2024:5433
Frequently asked(5)
What is CVE-2023-47108?
When was the CVE record for CVE-2023-47108 published?
Is CVE-2023-47108 actively exploited?
What is the CVSS score of CVE-2023-47108?
How do I remediate CVE-2023-47108?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-47108
Is Your Infrastructure Affected by CVE-2023-47108?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.