Summary
Kopia: Storage connection credentials written to console on "repository status" CLI command with JSON output
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
- Be aware that
kopia repo status --jsonwill write the credentials to the output without scrubbing them. - Avoid executing
kopia repo statuswith the--jsonflag in an insecure environment where. - Avoid logging the output of the
kopia repo status --jsoncommand.
Impact
What kind of vulnerability is it? Who is impacted?
Storage credentials are written to the console.
GHSA-J5VM-7QCC-2WWG has a CVSS score of 2.0 (Low). The vector is requires local access, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.16.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Has the problem been patched? Yes, see #3589
What versions should users upgrade to?
- Any version after or including commit 1d6f852cd6534f4bea978cbdc85c583803d79f77
- No release has been created yet.
Frequently Asked Questions
- What is GHSA-J5VM-7QCC-2WWG? GHSA-J5VM-7QCC-2WWG is a low-severity security vulnerability in github.com/kopia/kopia (go), affecting versions < 0.16.0. It is fixed in 0.16.0.
- How severe is GHSA-J5VM-7QCC-2WWG? GHSA-J5VM-7QCC-2WWG has a CVSS score of 2.0 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/kopia/kopia are affected by GHSA-J5VM-7QCC-2WWG? github.com/kopia/kopia (go) versions < 0.16.0 is affected.
- Is there a fix for GHSA-J5VM-7QCC-2WWG? Yes. GHSA-J5VM-7QCC-2WWG is fixed in 0.16.0. Upgrade to this version or later.
- Is GHSA-J5VM-7QCC-2WWG exploitable, and should I be worried? Whether GHSA-J5VM-7QCC-2WWG is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-J5VM-7QCC-2WWG is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-J5VM-7QCC-2WWG? Upgrade
github.com/kopia/kopiato 0.16.0 or later.