Skip to content
Fencer Intel
medium 6.2

GHSA-26hr-q2wp-rvc5 json

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

published 2y ago modified 8mo ago also GO-2023-2397

cvss
6.2
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

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.

Patch / fix

  • go github.com/treeverse/lakefs 1.3.1

Is GHSA-26hr-q2wp-rvc5 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 Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 6.2 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
go github.com/treeverse/lakefs
<1.3.1
1.3.1

References

Sources

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.