CVE-2024-32028

Sensitive-data exposure via unredacted query telemetry

Published Apr 12, 2024 · Updated Aug 2, 2024

Information exposure in OpenTelemetry .NET instrumentation before 1.8.1 allows attackers to send sensitive query data to telemetry backends. OpenTelemetry.Instrumentation.Http copies raw outbound query strings into url.full, while OpenTelemetry.Instrumentation.AspNetCore copies raw inbound queries into url.query without redacting parameter values. Exposure requires tracing and sensitive data in a request query; anyone able to read the telemetry backend can obtain those values.

CVSS severity4.1
Medium
EPSS probability0.29%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information exposure in OpenTelemetry .NET instrumentation before 1.8.1 allows attackers to send sensitive query data to telemetry backends. OpenTelemetry.Instrumentation.Http copies raw outbound query strings into url.full, while OpenTelemetry.Instrumentation.AspNetCore copies raw inbound queries into url.query without redacting parameter values. Exposure requires tracing and sensitive data in a request query; anyone able to read the telemetry backend can obtain those values.

The record

CVE
CVE-2024-32028
Published
Apr 12, 2024
Updated
Aug 2, 2024
Vendor
OpenTelemetry
Product
OpenTelemetry
Classifications
CWE-212, CWE-201
Attack vector
adjacent
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 12, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.8.1

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesauthenticated

What is affected?

OpenTelemetry · OpenTelemetryversion=0 <1.8.1
OpenTelemetry · OpenTelemetry .NETversion=< 1.8.1

Published CVSS scores

4.1OpenTelemetryCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-212Improper Removal of Sensitive Information Before Storage or Transfer
CWE-201Insertion of Sensitive Information Into Sent Data

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo