Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-fvv5-h29g-f6w5
No affected components available
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:ReadActionenabled for the repository. Predefined policies RepoManagementRead and RepoManagementFullAccess allow this action.fs:ReadObjectandfs:WriteObjectenabled for some path.fs:ReadObjectnot 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
The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard