CVE-2022-21646 – github.com/authzed/spicedb

Package

Manager: go
Name: github.com/authzed/spicedb
Vulnerable Version: =1.3.0 || >=1.3.0 <1.4.0

Severity

Level: High

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

EPSS: 0.00343 pctl0.56262

Details

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: ```zed 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: * Open an issue in [SpiceDB](https://github.com/authzed/spicedb) * Ask a question in the [SpiceDB Discord](https://authzed.com/discord)

Metadata

Created: 2022-01-13T15:05:41Z
Modified: 2022-01-13T15:02:31Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/01/GHSA-7p8f-8hjm-wm92/GHSA-7p8f-8hjm-wm92.json
CWE IDs: ["CWE-155", "CWE-20"]
Alternative ID: GHSA-7p8f-8hjm-wm92
Finding: F026
Auto approve: 1