GitHub Advisoryadvisory · Go

GHSA-7p8f-8hjm-wm92 Lookup operations do not take into account wildcards in SpiceDB

HIGH Published 2022-01-13 Modified 2022-01-13 Official page ↗
Aliases
CVE-2022-21646
Ecosystem
Go
Packages
github.com/authzed/spicedb
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Weaknesses
CWE-155, CWE-20
Reviewed
2022-01-11

Affected packages

• Go github.com/authzed/spicedb: >= 1.3.0, < 1.4.0 → fixed in 1.4.0

Description

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 • Ask a question in the SpiceDB Discord

Related

Alias · CVE (1)

  • CVE-2022-21646 SpiceDB is a database system for managing security-critical application permissions. vulnerability

Weakness · CWE (2)

  • CWE-155 Improper Neutralization of Wildcards or Matching Symbols weakness
  • CWE-20 Improper Input Validation weakness

References