GHSA-j5vm-7qcc-2wwg: Kopia Storage Connection Credentials Written To Vulnerability

LOW
CVSS 2.0
CWE-200
Published
Advisory Summary

GHSA-j5vm-7qcc-2wwg is a LOW (CVSS 2.0) storage connection credentials written to vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Kopia libraries in the Go ecosystem. The issue involves storage connection credentials written to console on "repository status" cli command with json output. Remediation is available by upgrading affected packages to version 0.16.0.

GHSA-j5vm-7qcc-2wwg at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-j5vm-7qcc-2wwg
Severity LOW
CVSS v3.1 Base Score 2.0
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Kopia
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 2.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix GHSA-j5vm-7qcc-2wwg

To remediate this vulnerability, upgrade all affected Kopia dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/kopia/kopia fixed: 0.16.0
Upgrade github.com/kopia/kopia to 0.16.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/kopia/kopia

How to Check if You Are Affected

To determine whether your application is affected by GHSA-j5vm-7qcc-2wwg, inspect your project dependencies for Kopia:

inspect dependencies for github.com/kopia/kopia

Analyze the terminal output to locate any version of Kopia in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.16.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Kopia, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

GHSA-j5vm-7qcc-2wwg Affected Kopia Versions

1 component(s)
Fixed Versions:
0.16.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/kopia/kopia
Go
< 0.16.0
0.16.0

References

Frequently Asked Questions

What is GHSA-j5vm-7qcc-2wwg?
GHSA-j5vm-7qcc-2wwg is a security vulnerability in Kopia involving Storage connection credentials written to console on "repository status" CLI command with JSON output under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Kopia versions are affected?
Affected versions include releases prior to 0.16.0 across affected packages: github.com/kopia/kopia.
What version fixes GHSA-j5vm-7qcc-2wwg?
Upgrading to 0.16.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/kopia/kopia affected?
Yes, github.com/kopia/kopia is affected in releases prior to 0.16.0. Upgrade your dependency to 0.16.0 or later.
What is the CVSS score of GHSA-j5vm-7qcc-2wwg?
GHSA-j5vm-7qcc-2wwg has a CVSS v3.1 base score of 2.0 (LOW) with vector string CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N.
What CWE is associated with GHSA-j5vm-7qcc-2wwg?
GHSA-j5vm-7qcc-2wwg is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Go dependencies for GHSA-j5vm-7qcc-2wwg?
Run the dependency tree command: 'inspect dependencies for github.com/kopia/kopia'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j5vm-7qcc-2wwg",
  "modified" : "2026-04-27T14:18:23Z",
  "published" : "2024-04-10T17:15:26Z",
  "aliases" : [ ],
  "summary" : "Kopia: Storage connection credentials written to console on \"repository status\" CLI command with JSON output",
  "details" : "### Impact\n\n_What kind of vulnerability is it? Who is impacted?_\n\nStorage credentials are written to the console.\n\n### Patches\n\n_Has the problem been patched?_ Yes, see #3589\n_What versions should users upgrade to?_\n- Any version after or including commit 1d6f852cd6534f4bea978cbdc85c583803d79f77\n- No release has been created yet.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n- Be aware that `kopia repo status --json` will write the credentials to the output without scrubbing them.\n- Avoid executing `kopia repo status` with the `--json` flag in an insecure environment where.\n- Avoid logging the output of the `kopia repo status --json` command.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/kopia/kopia"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.16.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kopia/kopia/security/advisories/GHSA-j5vm-7qcc-2wwg"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kopia/kopia/pull/3589"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kopia/kopia/commit/1d6f852cd6534f4bea978cbdc85c583803d79f77"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kopia/kopia"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-04-10T17:15:26Z",
    "nvd_published_at" : null
  }
}