GHSA-j5vm-7qcc-2wwg Kopia: Storage connection credentials written to console on "repository status" CLI command with JSON output
Kopia CLI exposes storage credentials in console output when using JSON format, allowing local attackers to steal sensitive repository access keys.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is GHSA-j5vm-7qcc-2wwg?
GHSA-j5vm-7qcc-2wwg is a vulnerability in github.com/kopia/kopia, published on 10 Apr 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
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 --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.
Which versions are affected by GHSA-j5vm-7qcc-2wwg?
3 open source packages ship an affected version, including github.com/kopia/kopia.
| Package | Affected | Fixed in |
|---|---|---|
github.com/kopia/kopia Go | All versions | 0.16.0 |
github.com/kopia/kopia Go | All versions | 0.16.0 |
github.com/kopia/kopia Go | All versions | 0.16.0 |
How do I fix GHSA-j5vm-7qcc-2wwg?
Upgrade github.com/kopia/kopia to 0.16.0 or later.
Is GHSA-j5vm-7qcc-2wwg being exploited?
There is no known exploitation of GHSA-j5vm-7qcc-2wwg in the wild and no public exploit code.
Sources
Also known as GO-2024-2703.