CVE-2024-32028

MEDIUMNVD 4.14.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 4.1 under NVD CVSS v3. EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
4.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OpenTelemetry dotnet is a dotnet telemetry framework. In affected versions of OpenTelemetry.Instrumentation.Http and OpenTelemetry.Instrumentation.AspNetCore the url.full writes attribute/tag on spans (Activity) when tracing is enabled for outgoing http requests and OpenTelemetry.Instrumentation.AspNetCore writes the url.query attribute/tag on spans (Activity) when tracing is enabled for incoming http requests. These attributes are defined by the Semantic Conventions for HTTP Spans. Up until version 1.8.1 the values written by OpenTelemetry.Instrumentation.Http & OpenTelemetry.Instrumentation.AspNetCore will pass-through the raw query string as was sent or received (respectively). This may lead to sensitive information (e.g. EUII - End User Identifiable Information, credentials, etc.) being leaked into telemetry backends (depending on the application(s) being instrumented) which could cause privacy and/or security incidents. Note: Older versions of OpenTelemetry.Instrumentation.Http & OpenTelemetry.Instrumentation.AspNetCore may use different tag names but have the same vulnerability. The 1.8.1 versions of OpenTelemetry.Instrumentation.Http & OpenTelemetry.Instrumentation.AspNetCore will now redact by default all values detected on transmitted or received query strings. Users are advised to upgrade. There are no known workarounds for this vulnerability.

CVSS v3
4.1
EG Score
4.1MEDIUMmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity41% × 45%
The EG Score, 4.1 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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
0.3%
EPSS %ILE
20th
KEV
Not listed

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 none (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.

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

April 12, 2024

Last Modified

April 15, 2026

References (3)

Affected Packages

(2 across 1 ecosystem)
NuGet(2)
PackageVulnerable rangeFix by version rangeDependents
OpenTelemetry.Instrumentation.AspNetCore1.0.0-rc10 ... 1.8.0 (13 versions)
  • every version up to 1.8.1: fixed in 1.8.1
—
OpenTelemetry.Instrumentation.Http1.0.0-rc10 ... 1.8.0 (13 versions)
  • every version up to 1.8.1: fixed in 1.8.1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 33× 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 91 of 211 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. 9 repeat rows among the latest 100 are merged into the row they repeat. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-12 17:55 UTCEG score recompute
  5. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-11 21:20 UTCEG score recompute
  7. 2026-10-11 16:13 UTCEG score recompute
  8. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-07 14:05 UTCOSV refresh
  14. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-09-30 19:43 UTCEG score recompute
  20. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-09-27 13:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.3% · 19th percentile
Show 66 more
  1. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-09-17 20:06 UTCOSV refresh
  8. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  10. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  15. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  16. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  17. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  18. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  19. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  20. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  21. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  22. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-08-29 20:13 UTCOSV refresh
  25. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  26. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  27. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  29. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  30. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  31. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  34. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  35. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  38. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  39. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  40. 2026-08-13 07:05 UTCOSV refresh
  41. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  42. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  43. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  44. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  45. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  46. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  47. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  48. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  49. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  50. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  51. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  52. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  53. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  54. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  55. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  56. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  57. 2026-07-28 15:21 UTCOSV refresh
  58. 2026-07-27 14:11 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  59. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  60. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  61. 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  62. 2026-07-23 14:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  63. 2026-07-23 02:36 UTCEG score recompute
  64. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  65. 2026-07-20 17:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  66. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-32028?
CVE-2024-32028 is a medium-severity vulnerability; its CVE record was published on April 12, 2024. OpenTelemetry dotnet is a dotnet telemetry framework. In affected versions of OpenTelemetry.Instrumentation.Http and OpenTelemetry.Instrumentation.AspNetCore the url.full writes attribute/tag on spans (Activity) when tracing is enabled for outgoing http requests and…
When was the CVE record for CVE-2024-32028 published?
The CVE record for CVE-2024-32028 was published on April 12, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-32028 actively exploited?
CVE-2024-32028 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-32028?
CVE-2024-32028 has a CVSS v3 base score of 4.1 (NVD).
How do I remediate CVE-2024-32028?
A fix for CVE-2024-32028 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-32028

Explore →

Is Your Infrastructure Affected by CVE-2024-32028?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs