| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/treeverse/lakefs | ≥ 0.90.0, < 1.12.1 | 1.12.1 |
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:
ci:ReadAction enabled for the repository. Predefined policies RepoManagementRead and RepoManagementFullAccess allow this action.fs:ReadObject and fs:WriteObject enabled for some path.fs:ReadObject not available for some pathSuch 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.
Releases >= 1.12.1 fix this issue in lakeFS.
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:
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free