github.com/authzed/spicedb
Affected
- introduced
0, fixed1.35.3(semver)
Fixed versions
1.35.3
Fix
- Fixed version
1.35.3go get github.com/authzed/[email protected]
Advisory
Also known as: CVE-2024-46989, GO-2024-3131
SpiceDB having multiple caveats on resources of the same type may improperly result in no permission
Background
Multiple caveats over the same indirect subject type on the same relation can result in no permission being returned when permission is expected
For example, given this schema:
definition user {}
caveat somecaveat(somefield int) {
somefield == 42
}
definition group {
relation member: user
}
definition resource {
relation viewer: group#member with somecaveat
permission view = folder->view
}
If the resource has multiple groups, and each group is caveated, it is possible for the returned permission to be "no permission" when permission is expected.
Impact
Permission is returned as NO_PERMISSION when PERMISSION is expected on the CheckPermission API.
Workarounds
Do not use caveats or do not use caveats on an indirect subject type with multiple entries
Medium Basis: The source's own band: MODERATE
0, fixed 1.35.3 (semver)1.35.3
1.35.3go 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