What is the CVSS score of CVE-2023-29193?

CVE-2023-29193 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.8%.

Is there a patch available for CVE-2023-29193?

Yes, a patch is available for CVE-2023-29193. Update the affected software to the latest version immediately.

Spicedb CVE-2023-29193

HIGH

Error Message Information Leak (CWE-209)

2023-04-14 security-advisories@github.com

Information Disclosure Google Spicedb

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Apr 14, 2023 - 20:15 nvd

HIGH 7.5

DescriptionNVD

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.

AnalysisAI

SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity.

Technical ContextAI

This vulnerability is classified under CWE-209. 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. Affected products include: Authzed Spicedb. Version information: version 1.19.1..

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.