github.com/treeverse/lakefs
Affected
- introduced
0.90.0, fixed1.12.1(semver)
Fixed versions
1.12.1
Fix
- Fixed version
1.12.1go get github.com/treeverse/[email protected]
Advisory
Also known as: GO-2024-2581
User with ci:ReadAction permissions and write permissions to one path in a repository may copy objects from any path in the repository
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:
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.
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:
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
Medium Basis: The source's own band: MODERATE
0.90.0, fixed 1.12.1 (semver)1.12.1
1.12.1go get github.com/treeverse/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0