SpiceDB is a database system for managing security-critical application permissions. 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. In `v1.3.0`, the wildcard is ignored entirely in lookup's dispatch, resulting in the `banned` wildcard being ignored in the exclusion. Version 1.4.0 contains a patch for this issue. As a workaround, don't make use of wildcards on the right side of intersections or within exclusions.
References
Link | Resource |
---|---|
https://github.com/authzed/spicedb/issues/358 | Third Party Advisory |
https://github.com/authzed/spicedb/releases/tag/v1.4.0 | Release Notes Third Party Advisory |
https://github.com/authzed/spicedb/security/advisories/GHSA-7p8f-8hjm-wm92 | Third Party Advisory |
https://github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970 | Patch Third Party Advisory |
Configurations
Information
Published : 2022-01-11 14:15
Updated : 2022-01-21 07:17
NVD link : CVE-2022-21646
Mitre link : CVE-2022-21646
JSON object : View
CWE
CWE-20
Improper Input Validation
Products Affected
authzed
- spicedb