CVE-2023-29193
HIGHDescription
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 or the SpiceDB Operator ### References - GitHub Security Advisory issued for SpiceDB - Go issue #22085 for documenting the risks of exposing pprof to the internet - Go issue #42834 discusses preventing pprof registration to the default serve mux - semgrep rule go.lang.security.audit.net.pprof.pprof-debug-exposure 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.
How to fix
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Exploit Intelligence
Moderate risk: more likely to be exploited than 51% of all known CVEs.
References
Related Vulnerabilities
Other CWE-209 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-29059 | High | 7.5 | 99% | KEV | - |
| CVE-2021-22145 | Medium | 6.5 | 76% | - | - |
| CVE-2010-3332 | Medium | 6.4 | 67% | - | - |
| CVE-2025-62168 | Critical | 10.0 | 63% | - | Fix |
| CVE-2013-7331 | Medium | 6.5 | 58% | KEV | - |
| CVE-2025-47813 | Medium | 4.3 | 56% | KEV | Fix |
Embed a live status badge for CVE-2023-29193
Markdown
[](https://tridentstack.com/cve/CVE-2023-29193)HTML
<a href="https://tridentstack.com/cve/CVE-2023-29193"><img src="https://tridentstack.com/cve/badge/CVE-2023-29193.svg" alt="CVE-2023-29193"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
Start freeThis product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.