Skip to content

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

Low severity GitHub Reviewed Published Apr 9, 2024 in kopia/kopia • Updated Apr 10, 2024

Package

gomod github.com/kopia/kopia (Go)

Affected versions

< 0.16.0

Patched versions

0.16.0

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

References

@julio-lopez julio-lopez published to kopia/kopia Apr 9, 2024
Published to the GitHub Advisory Database Apr 10, 2024
Reviewed Apr 10, 2024
Last updated Apr 10, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-j5vm-7qcc-2wwg

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.