github.com/authzed/spicedb
Affected
- introduced
0, fixed1.19.1(semver)
Fixed versions
1.19.1
Fix
- Fixed version
1.19.1go get github.com/authzed/[email protected]
Advisory
Also known as: CVE-2023-29193, GO-2023-1723
SpiceDB binding metrics port to untrusted networks and can leak command-line flags
Background
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.
Impact
All deployments abiding by the recommended best practices for production usage are NOT affected:
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.
Workarounds
To workaround this issue you can do one of the following:
SPICEDB_GRPC_PRESHARED_KEY=yoursecret spicedb serve)--metrics-addr flag to bind to a trusted network (e.g. --metrics-addr=localhost:9090)--metrics-enabled=false)References
High Basis: The source's own band: HIGH
0, fixed 1.19.1 (semver)1.19.1
1.19.1go get github.com/authzed/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0