dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2024-40636

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Steeltoe is an open source project that provides a collection of libraries that helps users build production-grade cloud-native applications using externalized configuration, service discovery, distributed tracing, application management, and more. When utilizing multiple Eureka server service URLs with basic auth and encountering an issue with fetching the service registry, an error is logged with the Eureka server service URLs but only the first URL is masked. The code in question is `_logger.LogError(e, "FetchRegistry Failed for Eureka service urls: {EurekaServerServiceUrls}", new Uri(ClientConfig.EurekaServerServiceUrls).ToMaskedString());` in the `DiscoveryClient.cs` file which may leak credentials into logs. This issue has been addressed in version 3.2.8 of the Steeltoe.Discovery.Eureka nuget package.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

When the Steeltoe Discovery Client logs errors while fetching the Eureka service registry with multiple Eureka server URLs configured with basic authentication, only the first URL gets masked by ToMaskedString(), leaving subsequent URLs with exposed credentials (username:password) in application logs.

MitigationUpgrade the Steeltoe.Discovery.Eureka nuget package to version 3.2.8 or later which properly masks all Eureka server URLs in log output.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Steeltoe.Discovery.Eureka package version
    Inspect the project file (.csproj) or list installed NuGet packages to find the version of Steeltoe.Discovery.Eureka. Look for a line like <PackageReference Include="Steeltoe.Discovery.Eureka" Version="x.x.x" /> or use 'dotnet list package'
    Affected if The installed version is lower than 3.2.8 (e.g., 3.2.7, 3.2.0, 2.x, etc.)
  2. Verify multiple Eureka server URLs are configured
    Check application configuration files (appsettings.json, appsettings.{environment}.json, or YAML) for the 'eureka:client:serverList' or 'eureka:serverList' configuration section. Also check any environment-specific overrides.
    Affected if Two or more Eureka server URLs are listed in the configuration
  3. Confirm basic authentication is enabled for Eureka
    Inspect the same configuration files for 'eureka:client:username' and 'eureka:client:password' or equivalent basic auth settings under the Eureka server configuration section.
    Affected if Username and password credentials are configured for Eureka server authentication
  4. Review application logs for credential exposure
    Search existing application logs (file-based, console, or centralized logging) for entries containing Eureka server URLs. Look for error-level logs during service registry fetches.
    Affected if Logs contain URLs with visible username:password patterns (e.g., http://user:pass@server2:8761/eureka/) instead of masked credentials

You are affected if you use Steeltoe.Discovery.Eureka version lower than 3.2.8 with multiple Eureka server URLs configured and basic authentication enabled, and any error logs may contain exposed credentials for URLs beyond the first one.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Steeltoe.Discovery.Eureka nuget package to version 3.2.8 or later which properly masks all Eureka server URLs in log output.

Recommended fix High confidence

Steeltoe.Discovery.Eureka version 3.2.8

  1. Update the Steeltoe.Discovery.Eureka NuGet package reference in your project file (.csproj) to version 3.2.8 or later
  2. Run `dotnet restore` to fetch the updated package
  3. Rebuild and redeploy your application

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-40636 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data