dbcve.org
RetryablehttpApplication · Hashicorp

CVE-2024-6104

MEDIUM · 5.5 CVSS v3.1 Published 2024-06-24
Fix available
A fix is available. Upgrade to 0.7.7 or later.
See remediation →
57/100
Remediation priority · Elevated
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
go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.

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

go-retryablehttp versions before 0.7.7 do not sanitize URLs before writing them to log files. When URLs contain HTTP basic auth credentials (e.g., https://user:[email protected]), these credentials are written in plaintext to logs, leading to credential exposure.

MitigationUpgrade go-retryablehttp to version 0.7.7 or later. Audit existing log files for exposed credentials and rotate any compromised credentials.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RetryablehttpApplication
Affected:< 0.7.7

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Identify go-retryablehttp version
    Run 'go list -m all | grep retryablehttp' in your project directory, or check your go.mod/go.sum file for the retryablehttp version entry
    Affected if The version listed is before 0.7.7 (e.g., 0.7.6, 0.7.5, etc.)
  2. Confirm logging is enabled
    Review your application configuration for logging settings. Check if a logger is passed to the retryablehttp.Client via the Logger field, or if default logging is active
    Affected if Logging is enabled and the retryablehttp client is configured with a logger
  3. Check if requests use basic authentication in URLs
    Search your application code for URLs containing credentials in the format https://user:pass@host, or review how your application constructs request URLs
    Affected if Your application passes credentials via URL (user:pass@hostname) rather than using the Authorization header
  4. Inspect log files for exposed credentials
    Search your application log files for patterns matching user:pass@, or grep for ':@' within URLs. Example: grep -E '://[^:]+:[^@]+@' /path/to/logs/*.log
    Affected if Log files contain plaintext basic auth credentials in URLs (e.g., https://myuser:[email protected])

You are affected if your environment uses go-retryablehttp version 0.7.7 or earlier AND your application logs URLs that include HTTP basic auth credentials in the format user:pass@host.

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
Upgrade available Upgrade to 0.7.7 or later
Fixed in 0.7.7
Interim mitigation

Upgrade go-retryablehttp to version 0.7.7 or later. Audit existing log files for exposed credentials and rotate any compromised credentials.

Recommended fix High confidence

go-retryablehttp v0.7.7

  1. Update the go-retryablehttp dependency to version 0.7.7 or later by running: go get github.com/hashicorp/[email protected]
  2. Verify the correct version is installed by running: go list -m github.com/hashicorp/go-retryablehttp
  3. Run go mod tidy to clean up dependencies
  4. Rebuild and test the application to ensure the upgrade does not break existing functionality
Caveat Review the release notes for 0.7.7 to check for any breaking changes before upgrading

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

Fix this in Retryablehttp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6104 — 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-6104 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