Skip to content
Fencer Intel
medium 5.3

GHSA-fvv5-h29g-f6w5 json

User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository

published 2y ago modified 8mo ago also GO-2024-2581

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

A bug in permissions validation allows a user with the `ci:ReadAction` permission to skip read checks when copying an object. If they additionally have read and write permission to path in the repository, they can copy an otherwise unreadable object and read it.

In order to be affected and exploitable, the following conditions must ALL occur on the same user: 1. `ci:ReadAction` enabled for the repository. Predefined policies RepoManagementRead and RepoManagementFullAccess allow this action. 2. `fs:ReadObject` and `fs:WriteObject` enabled for some path. 3. `fs:ReadObject` _not_ available for some path

Such a user can use (1) to copy the unreadable object (3) to a path that they can read and write (2). At that point they can read the object copy.

### Patches

Releases >= 1.12.1 fix this issue in lakeFS.

### Workarounds

As a workaround, use RBAC to deny `ci:*` permissions to all users, or to all users who have limited read access.

Many installations are unaffected:

* **Installations using ACLs are _not_ affected.** This includes all OSS installations that have not implemented an external authorization server. We do not know of any OSS installations that have implemented such a server. ACLs that allow ci:ReadAction also allow reading repositories, so no capabilities are granted. * **Installations using RBAC that use only predefined policies with "all" ARNs ("*") are _not_ affected.** This includes **all installations that have not defined any new groups in RBAC.**

In order to be affected, **installations using RBAC** must define users and simultaneous allow `ci:ReadAction` and disallow `fs:ReadObject` for some path. `ci:ReadAction` is available in policies RepoManagementReadAll and RepoManagementFullAccess. By default these actions are configured for groups Developers and above, for all repositories and paths.

### References

* [lakeFS RBAC](https://docs.lakefs.io/reference/security/rbac.html)

Patch / fix

  • go github.com/treeverse/lakefs 1.12.1

Is GHSA-fvv5-h29g-f6w5 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 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/treeverse/lakefs
>=0.90.0, <1.12.1
1.12.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.