GHSA-j5vm-7qcc-2wwg json
Kopia: Storage connection credentials written to console on "repository status" CLI command with JSON output
published 2y ago modified 2mo ago also GO-2024-2703
- cvss
- 2.0
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### 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.
Patch / fix
- go github.com/kopia/kopia 0.16.0
- github.com/kopia/kopia@1d6f852 commit
- github.com/kopia/kopia#3589 pull request
Is GHSA-j5vm-7qcc-2wwg in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 2.0 | CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/kopia/kopia | <0.16.0 |
0.16.0 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
Sources
- GitHub Advisory GHSA-j5vm-7qcc-2wwg
- OSV GO-2024-2703
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.