dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2024-8986

CRITICAL · 9.1 CVSS v4.0 Published 2024-09-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The grafana plugin SDK bundles build metadata into the binaries it compiles; this metadata includes the repository URI for the plugin being built, as retrieved by running `git remote get-url origin`. If credentials are included in the repository URI (for instance, to allow for fetching of private dependencies), the final binary will contain the full URI, including said credentials.

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

The Grafana plugin SDK embeds git repository URLs obtained via 'git remote get-url origin' into compiled plugin binaries. If the git remote URL contains embedded credentials (e.g., https://username:[email protected]/org/repo for private dependencies), those credentials will be hardcoded and extractable from the final binary.

MitigationRemove embedded credentials from git remote URLs before building; use git credential helpers, environment variables, or CI/CD secrets instead of embedding credentials directly in repository URLs. Rebuild any previously-compiled binaries that may contain exposed credentials.

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
Authentication
Y
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:X/RE:L/U:X

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 Grafana plugin SDK usage
    Inspect your project for Grafana plugin build artifacts: look for go.mod containing grafana-plugin-sdk-go, or check for Makefile/build scripts that use grafana-cli or grafana-plugin-model. Check if the project directory contains typical Grafana plugin structure (plugin.json, or src/ with plugin code).
    Affected if You are actively building or have built Grafana plugins using the Grafana plugin SDK
  2. Examine git remote URL for embedded credentials
    Run 'git remote -v' and 'git remote get-url origin' in your project directory. Inspect the output for credential patterns: look for '://' followed by username:password@ before the hostname. Examples: https://user:[email protected], http://token:[email protected]
    Affected if The git remote URL contains embedded username:password or token in the format scheme://credentials@hostname
  3. Search compiled binaries for credential patterns
    If you have built plugin binaries (.so, .dll, or bundled JS files), use strings/grep to search for your git hostname within the binary. Example: 'strings plugin.so | grep github.com' or inspect minified JS bundles. Look for the full git remote URL pattern including any credentials.
    Affected if The compiled binary contains the full git remote URL including credentials from your git remote configuration
  4. Audit build artifacts for exposed secrets
    Review any build output files, including dist/ folders, compiled binaries, and frontend assets (webpack bundles). Search these files for your git username, password, or token values that were used in the git remote URL.
    Affected if Build artifacts contain the credentials that were in your git remote URL

You are affected if you built Grafana plugin binaries using the Grafana plugin SDK while your git remote origin URL contained embedded credentials (username:password or tokens), as those credentials are now extractable from your compiled binaries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove embedded credentials from git remote URLs before building; use git credential helpers, environment variables, or CI/CD secrets instead of embedding credentials directly in repository URLs. Rebuild any previously-compiled binaries that may contain exposed credentials.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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