8.7

CVE-2023-29193: authzed spicedb

CVSS: 8.7v3.1HighModified
AliasesCGA-2vvp-85m9-q6fhCGA-5x5j-627h-j585CGA-rff8-48fg-vwv3
Published 14-04-2023Last modified 06-02-2025

Vulnerability summary

CVE-2023-29193 is a high (CVSS 8.7) vulnerability in authzed spicedb. EPSS estimates a 0.76% chance of exploitation in the next 30 days, higher than 54.6% of scored vulnerabilities.

Overall risk
35/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.7/10
010
High · v3.1 (CVE.org)
EPSS score
0.76%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 0 · Related 2

Timeline

  1. 14-04-2023
    PublishedVulnerability first disclosed.
  2. 06-02-2025
    Last modifiedVulnerability information updated.

Description

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. This issue has been fixed in version 1.19.1. ### Impact All deployments abiding by the recommended best practices for production usage are **NOT affected**: - Authzed's SpiceDB Serverless - Authzed's SpiceDB Dedicated - SpiceDB Operator Users configuring SpiceDB via environment variables are **NOT affected**. Users **MAY be affected** if they expose their metrics port to an untrusted network and are configuring `--grpc-preshared-key` via command-line flag. ### Patches TODO ### Workarounds To workaround this issue you can do one of the following: - Configure the preshared key via an environment variable (e.g. `SPICEDB_GRPC_PRESHARED_KEY=yoursecret spicedb serve`) - Reconfigure the `--metrics-addr` flag to bind to a trusted network (e.g. `--metrics-addr=localhost:9090`) - Disable the metrics service via the flag (e.g. `--metrics-enabled=false`) - Adopt one of the recommended deployment models: [Authzed's managed services](https://authzed.com/pricing) or the [SpiceDB Operator](https://github.com/authzed/spicedb-operator) ### References - [GitHub Security Advisory issued for SpiceDB](https://github.com/authzed/spicedb/security/advisories/GHSA-cjr9-mr35-7xh6) - [Go issue #22085](https://github.com/golang/go/issues/22085) for documenting the risks of exposing pprof to the internet - [Go issue #42834](https://github.com/golang/go/issues/42834) discusses preventing pprof registration to the default serve mux - [semgrep rule go.lang.security.audit.net.pprof.pprof-debug-exposure](https://semgrep.dev/r?q=go.lang.security.audit.net.pprof) checks for a variation of this issue ### Credit We'd like to thank Amit Laish, a security researcher at GE Vernova for responsibly disclosing this vulnerability.

CVSS metrics

5 scores · 5 sources · 1 version

EPSS trend

Probability

0.76%

Chance of exploitation in the next 30 days

Percentile

55%

Versus all other CVEs

30-day change

0.00 pp

From 0.76% on 20-09-2026

20-09-202620-10-2026
EPSS score
0.76%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Chainguard2 products
  • spicedb< 1.33.0-r0
  • spicedb-compat< 1.33.0-r0
Wolfi2 products
  • spicedb< 1.33.0-r0
  • spicedb-compat< 1.33.0-r0
Authzed1 product
Github.com/authzed1 product
  • spicedb< 1.19.1

4 vendors · 6 products

References

6 links