Page 2 of 8 results (0.006 seconds)

CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 0

SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions. Any user making a negative authorization decision based on the results of a `LookupResources` request with 1.22.0 is affected. For example, using `LookupResources` to find a list of resources to allow access to be okay: some subjects that should have access to a resource may not. But if using `LookupResources` to find a list of banned resources instead, then some users that shouldn't have access may. Generally, `LookupResources` is not and should not be to gate access in this way - that's what the `Check` API is for. • https://github.com/authzed/spicedb/pull/1397 https://github.com/authzed/spicedb/security/advisories/GHSA-m54h-5x5f-5m6r • CWE-913: Improper Control of Dynamically-Managed Code Resources •

CVSS: 8.7EPSS: 0%CPEs: 1EXPL: 0

SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions. The `spicedb serve` command contains a flag named `--grpc-preshared-key` which is used to protect the gRPC API from being accessed by unauthorized requests. The values of this flag are to be considered sensitive, secret data. The `/debug/pprof/cmdline` endpoint served by the metrics service (defaulting running on port `9090`) reveals the command-line flags provided for debugging purposes. If a password is set via the `--grpc-preshared-key` then the key is revealed by this endpoint along with any other flags provided to the SpiceDB binary. • https://github.com/authzed/spicedb/commit/9bbd7d76b6eaba33fe0236014f9b175d21232999 https://github.com/authzed/spicedb/releases/tag/v1.19.1 https://github.com/authzed/spicedb/security/advisories/GHSA-cjr9-mr35-7xh6 • CWE-209: Generation of Error Message Containing Sensitive Information •

CVSS: 8.1EPSS: 0%CPEs: 1EXPL: 0

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. • https://github.com/authzed/spicedb/commit/15bba2e2d2a4bda336a37a7fe8ef8a35028cd970 https://github.com/authzed/spicedb/issues/358 https://github.com/authzed/spicedb/releases/tag/v1.4.0 https://github.com/authzed/spicedb/security/advisories/GHSA-7p8f-8hjm-wm92 • CWE-20: Improper Input Validation CWE-155: Improper Neutralization of Wildcards or Matching Symbols •