CVE-2022-21646
moderate-risk
Published 2022-01-11
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.
Do I need to act?
-
0.36% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
8
CVSS 8.1/10
High
NETWORK
/ LOW complexity
Affected Products (1)
Spicedb
Affected Vendors
References (8)
Third Party Advisory
https://github.com/authzed/spicedb/issues/358
Release Notes
https://github.com/authzed/spicedb/releases/tag/v1.4.0
Third Party Advisory
https://github.com/authzed/spicedb/security/advisories/GHSA-7p8f-8hjm-wm92
Third Party Advisory
https://github.com/authzed/spicedb/issues/358
Release Notes
https://github.com/authzed/spicedb/releases/tag/v1.4.0
Third Party Advisory
https://github.com/authzed/spicedb/security/advisories/GHSA-7p8f-8hjm-wm92
34
/ 100
moderate-risk
Severity
28/34 · Critical
Exploitability
1/34 · Minimal
Exposure
5/34 · Minimal