Lookup operations do not take into account wildcards in SpiceDB
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
github.com/authzed/spicedbGo | >= 1.3.0, < 1.4.0 | 1.4.0 |
Affected products
2Patches
Vulnerability mechanics
References
6- github.com/advisories/GHSA-7p8f-8hjm-wm92ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2022-21646ghsaADVISORY
- github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970ghsax_refsource_MISCWEB
- github.com/authzed/spicedb/issues/358ghsax_refsource_MISCWEB
- github.com/authzed/spicedb/releases/tag/v1.4.0ghsax_refsource_MISCWEB
- github.com/authzed/spicedb/security/advisories/GHSA-7p8f-8hjm-wm92ghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.