Credential disclosure via embedded repository URL
Published Sep 19, 2024 · Updated Sep 19, 2024
Credential exposure in Grafana Plugin SDK for Go 0.106.0 through 0.249.0 allows attackers to recover repository credentials from plugin binaries. The build.Info path reads the origin URL from CI variables or git remote get-url origin and serializes it into buildInfoJSON linker data without removing embedded credentials. Exposure requires a credential-bearing repository URL and access to the compiled plugin binary; Grafana binaries built with the SDK are unaffected.
Summary
What happened
Credential exposure in Grafana Plugin SDK for Go 0.106.0 through 0.249.0 allows attackers to recover repository credentials from plugin binaries. The build.Info path reads the origin URL from CI variables or git remote get-url origin and serializes it into buildInfoJSON linker data without removing embedded credentials. Exposure requires a credential-bearing repository URL and access to the compiled plugin binary; Grafana binaries built with the SDK are unaffected.
The record
- CVE
- CVE-2024-8986
- Published
- Sep 19, 2024
- Updated
- Sep 19, 2024
- Vendor
- Grafana Labs
- Product
- Grafana Plugin SDK for Go
- Classifications
- CWE-522, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2024CVE publishedPublication date reported by the CVE source.
- Sep 19, 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.
- Affected versionversion=0.106.0 <=0.249.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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