Skip to content

User with permission to write actions can impersonate another user when auth token is configured in environment variable

Moderate severity GitHub Reviewed Published Dec 10, 2023 in treeverse/lakeFS • Updated Dec 12, 2023

Package

gomod github.com/treeverse/lakefs (Go)

Affected versions

< 1.3.1

Patched versions

1.3.1

Description

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.

  • Disable actions.

  • Limit users allowed to configure actions.

References

@nopcoder nopcoder published to treeverse/lakeFS Dec 10, 2023
Published to the GitHub Advisory Database Dec 12, 2023
Reviewed Dec 12, 2023
Last updated Dec 12, 2023

Severity

Moderate

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
Network
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

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:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:L

Weaknesses

No CWEs

CVE ID

No known CVE

GHSA ID

GHSA-26hr-q2wp-rvc5

Source code

Credits

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