github.com/authzed/spicedb
Affected
- introduced
1.3.0, fixed1.4.0(semver)
Fixed versions
1.4.0
Fix
- Fixed version
1.4.0go get github.com/authzed/[email protected]
Advisory
Also known as: CVE-2022-21646, GO-2022-0295
Lookup operations do not take into account wildcards in SpiceDB
Impact
Any user making use of a wildcard relationship under the right hand branch of an exclusion or within an intersection operation will see Lookup/LookupResources return a resource as "accessible" if it is *not* accessible by virtue of the inclusion of the wildcard in the intersection or the right side of the exclusion.
For example, given schema:
definition user {}
definition resource {
relation viewer: user
relation banned: user | user:*
permission view = viewer - banned
}
If user:* is placed into the banned relation for a particular resource, view should return false for *all* resources. in v1.3.0, the wildcard is ignored entirely in lookup's dispatch, resulting in the banned wildcard being ignored in the exclusion.
Workarounds
Don't make use of wildcards on the right side of intersections or within exclusions.
References
https://github.com/authzed/spicedb/issues/358
For more information
If you have any questions or comments about this advisory:
High Basis: The source's own band: HIGH
1.3.0, fixed 1.4.0 (semver)1.4.0
1.4.0go 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