GHSA-26hr-q2wp-rvc5: Github.com/treeverse/lakefs User With Permission To Write Vulnerability

MODERATE
Share
CVSS 6.2
Published
Advisory Summary

GHSA-26hr-q2wp-rvc5 is a MODERATE (CVSS 6.2) user with permission to write vulnerability (General Security Weakness) affecting Github.com/treeverse/lakefs libraries in the Go ecosystem. The issue involves user with permission to write actions can impersonate another user when auth token is configured in environment variable. Remediation is available by upgrading affected packages to version 1.3.1.

GHSA-26hr-q2wp-rvc5 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-26hr-q2wp-rvc5
Severity MODERATE
CVSS v3.1 Base Score 6.2
CWE Classification General Security Weakness
Affected Product Github.com/treeverse/lakefs
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.2

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

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

How to Fix GHSA-26hr-q2wp-rvc5

To remediate this vulnerability, upgrade all affected Github.com/treeverse/lakefs 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/treeverse/lakefs fixed: 1.3.1 
Upgrade github.com/treeverse/lakefs to 1.3.1
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/treeverse/lakefs

How to Check if You Are Affected

To determine whether your application is affected by GHSA-26hr-q2wp-rvc5, inspect your project dependencies for Github.com/treeverse/lakefs:

inspect dependencies for github.com/treeverse/lakefs

Analyze the terminal output to locate any version of Github.com/treeverse/lakefs in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.3.1), 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 General Security Weakness. In Github.com/treeverse/lakefs, 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 When lakeFS is configured with **ALL** of the following: - Configuration option `auth.encrypt.secret_key` passed through environment variable - Actions enabled via configuration option `actions.enabled` (default enabled) then a user who can configure an action can impersonate any other user. ### Patches _Has the problem been patched? What versions should users upgrade to?_ ### Workarounds **ANY ONE** of these is sufficient to prevent the issue: * Do not pass `auth.encrypt.secret_key` through an environment variable. For instance, Kubernetes users can generate the entire configuration as a secret and mount that. This is described [here](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret). * Disable actions. * Limit users allowed to configure actions.

GHSA-26hr-q2wp-rvc5 Affected Github.com/treeverse/lakefs Versions

1 component(s)
Fixed Versions:
1.3.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/treeverse/lakefs
golang/github.com/treeverse/lakefs
Go
< 1.3.1
1.3.1

References

GitHub Advisory / Wiki ADVISORY
https://github.com/treeverse/lakeFS/security/advisories/GHSA-26hr-q2wp-rvc5
Github.com/treeverse/lakefs Source Repository REPOSITORY
https://github.com/treeverse/lakeFS

Frequently Asked Questions

What is GHSA-26hr-q2wp-rvc5?
GHSA-26hr-q2wp-rvc5 is a security vulnerability in Github.com/treeverse/lakefs involving User with permission to write actions can impersonate another user when auth token is configured in environment variable under General Security Weakness.
Which Github.com/treeverse/lakefs versions are affected?
Affected versions include releases prior to 1.3.1 across affected packages: github.com/treeverse/lakefs.
What version fixes GHSA-26hr-q2wp-rvc5?
Upgrading to 1.3.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/treeverse/lakefs affected?
Yes, github.com/treeverse/lakefs is affected in releases prior to 1.3.1. Upgrade your dependency to 1.3.1 or later.
What is the CVSS score of GHSA-26hr-q2wp-rvc5?
GHSA-26hr-q2wp-rvc5 has a CVSS v3.1 base score of 6.2 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:L.
What CWE is associated with GHSA-26hr-q2wp-rvc5?
GHSA-26hr-q2wp-rvc5 is classified under General Security Weakness.
How can I check Go dependencies for GHSA-26hr-q2wp-rvc5?
Run the dependency tree command: 'inspect dependencies for github.com/treeverse/lakefs'. 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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-26hr-q2wp-rvc5",
  "modified" : "2023-12-12T00:58:04Z",
  "published" : "2023-12-12T00:58:04Z",
  "aliases" : [ ],
  "summary" : "User with permission to write actions can impersonate another user when auth token is configured in environment variable",
  "details" : "### Impact\n\nWhen lakeFS is configured with **ALL** of the following:\n\n- Configuration option `auth.encrypt.secret_key` passed through environment variable\n- Actions enabled via configuration option `actions.enabled` (default enabled)\n\nthen a user who can configure an action can impersonate any other user.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\n### Workarounds\n\n**ANY ONE** of these is sufficient to prevent the issue:\n\n* Do not pass `auth.encrypt.secret_key` through an environment variable.\n\n   For instance, Kubernetes users can generate the entire configuration as a secret and mount that.  This is described [here](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret).\n* Disable actions.\n* Limit users allowed to configure actions.\n\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/treeverse/lakefs"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.3.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/treeverse/lakeFS/security/advisories/GHSA-26hr-q2wp-rvc5"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/treeverse/lakeFS"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-12-12T00:58:04Z",
    "nvd_published_at" : null
  }
}