Skip to content

SpiceDB binding metrics port to untrusted networks and can leak command-line flags

High severity GitHub Reviewed Published Apr 13, 2023 in authzed/spicedb • Updated Apr 14, 2023

Package

gomod github.com/authzed/spicedb (Go)

Affected versions

< 1.19.1

Patched versions

1.19.1

Description

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:

  • 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.

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

References

@jzelinskie jzelinskie published to authzed/spicedb Apr 13, 2023
Published to the GitHub Advisory Database Apr 13, 2023
Reviewed Apr 13, 2023
Published by the National Vulnerability Database Apr 14, 2023
Last updated Apr 14, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.150%
(52nd percentile)

Weaknesses

CVE ID

CVE-2023-29193

GHSA ID

GHSA-cjr9-mr35-7xh6

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.