github.com/authzed/spicedb
Affected
- introduced
0, fixed1.33.1(semver)
Fixed versions
1.33.1
Fix
- Fixed version
1.33.1go get github.com/authzed/[email protected]
Advisory
Also known as: CVE-2024-38361, GO-2024-2939
SpiceDB exclusions can result in no permission returned when permission expected
Background
Use of an exclusion under an arrow that has multiple resources may resolve to NO_PERMISSION when permission is expected.
For example, given this schema:
definition user {}
definition folder {
relation member: user
relation banned: user
permission view = member - banned
}
definition resource {
relation folder: folder
permission view = folder->view
}
If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned
Impact
Permission is returned as NO_PERMISSION when PERMISSION is expected on the CheckPermission API.
Workarounds
None
Medium Basis: The source's own band: MODERATE
0, fixed 1.33.1 (semver)1.33.1
1.33.1go get github.com/authzed/[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