Kopia: Storage connection credentials written to console on "repository status" CLI command with JSON output

Severity: low · CVSS 2 · Published 2024-04-10

### Impact

_What kind of vulnerability is it? Who is impacted?_

Storage credentials are written to the console.

### Patches

_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.

### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_

- Be aware that `kopia repo status --json` will write the credentials to the output without scrubbing them. - Avoid executing `kopia repo status` with the `--json` flag in an insecure environment where. - Avoid logging the output of the `kopia repo status --json` command.

Technologies: github.com/kopia/kopia (Go). Vendors: Go.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Low severity, with a CVSS score of 2, published 10 April 2024.
Which products and versions are affected?
github.com/kopia/kopia (Go) < 0.16.0.
Is there a fix for This vulnerability?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected?
Check whether you run github.com/kopia/kopia (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • github.com/kopia/kopia (Go) < 0.16.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.