Cyber Resilience

CVE-2024-32028

Info Disclosure

Info Disclosure
Published
12 April 2024
Modified
15 April 2026
CVSS Score v3.1 4.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
EPSS Score 0.0029 21th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2024-32028 is a medium-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability. Its CVSS base score is 4.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-201CWE-212

Related Threats

MITRE ATT&CK Enterprise Techniques

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
attack.mitre.org →
T1552.002 Credentials in Registry Credential Access
Adversaries may search the Registry on compromised systems for insecurely stored credentials.
attack.mitre.org →
T1552.004 Private Keys Credential Access
Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials.
attack.mitre.org →
T1552.006 Group Policy Preferences Credential Access
Adversaries may attempt to find unsecured credentials in Group Policy Preferences (GPP).
attack.mitre.org →
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-59955Shared CWE-201, CWE-212
CVE-2026-27640Shared CWE-212
CVE-2025-0011Shared CWE-212
CVE-2025-68131Shared CWE-212
CVE-2026-42186Shared CWE-212
CVE-2023-28834Shared CWE-212
CVE-2024-49997Shared CWE-212
CVE-2026-1732Shared CWE-212
CVE-2025-65965Shared CWE-212
CVE-2025-8860Shared CWE-212

Affected Assets

—
Older
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V14.2.3
  • V14.2.8
  • V14.3.3

Mitigating Controls (NIST 800-53 r5) AI

AC-4 Information Flow Enforcement good match

Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.

AC-3 Access Enforcement good match

Enforces authorizations on logical access so that sensitive data is not released to unauthorized recipients.

MP-6 Media Sanitization good match

Requires sanitization of media before disposal, release, or reuse, directly stopping sensitive information from remaining in resources made available to unauthorized parties.

SI-15 Information Output Filtering good match

Requires validation of outbound information to ensure sensitive content is not disclosed in responses or messages.

SI-19 De-identification good match

Mandates removal of specified PII elements from datasets before further use or sharing, addressing a subset of the improper-removal cases.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-10 mostly match
prevents

Directly addresses removal of confidential data from process memory and similar in-use contexts before exposure.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.

DE.CM-09 partial match
prevents

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

PR.DS-02 partial match
prevents

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.10 Information deletion full match
degrades

Explicit information-deletion control directly addresses improper removal of sensitive data.

A.8.11 Data masking full match
prevents

Data-masking techniques can substitute for removal when full deletion is impractical.

A.8.33 Test information mostly match
prevents

Test-data protection rules require sanitization of production data used in testing.

A.5.12 Classification of information partial match
mitigates

Classification identifies sensitive data so it is not inadvertently transmitted.

A.5.13 Labelling of information partial match
mitigates

Labelling makes sensitive data visible to developers and prevents accidental inclusion in outbound messages.

A.5.14 Information transfer partial match
mitigates

Information-transfer rules directly govern what data may be sent to external parties.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (3 rules)
  • V-248579 OL 8 must restrict access to the kernel message buffer. prevents CWE-212
  • V-248580 OL 8 must prevent kernel profiling by unprivileged users. prevents CWE-212
  • V-248551 A sticky bit must be set on all OL 8 public directories to prevent unauthorized and unintended information transferred via shared system resources. prevents CWE-212
Oracle Linux 9 (1 rule)
  • V-271745 OL 9 must restrict access to the kernel message buffer. prevents CWE-212
RHEL 8 (1 rule)
  • V-230269 RHEL 8 must restrict access to the kernel message buffer. prevents CWE-212

References