# CVE-2023-46255: `SPICEDB_DATASTORE_CONN_URI` is leaked when URI cannot be parsed

> Attackers with log access can read database credentials when SpiceDB logs malformed connection URIs, exposing sensitive passwords.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Oct 2023
- **Updated:** 5 Sep 2024
- **Also known as:** GHSA-jg7w-cxjv-98c2, GO-2023-2166

## What is CVE-2023-46255?

CVE-2023-46255 is a medium-severity vulnerability in authzed spicedb, published on 31 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

SpiceDB is an open source, Google Zanzibar-inspired database for creating and managing security-critical application permissions. Prior to version 1.27.0-rc1, when the provided datastore URI is malformed (e.g. by having a password which contains `:`) the full URI (including the provided password) is printed, so that the password is shown in the logs. Version 1.27.0-rc1 patches this issue.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2023-46255?

3 open source packages ship an affected version, including github.com/authzed/spicedb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/authzed/spicedb` | Go | All versions | 1.27.0-rc1 |
| `github.com/authzed/spicedb` | Go | All versions | 1.27.0-rc1 |
| `github.com/authzed/spicedb` | Go | All versions | 1.27.0-rc1 |

Products: Authzed Spicedb.

## How do I fix CVE-2023-46255?

Upgrade github.com/authzed/spicedb to 1.27.0-rc1 or later.

## Is CVE-2023-46255 being exploited?

There is no known exploitation of CVE-2023-46255 in the wild and no public exploit code.

## Other vulnerabilities in authzed spicedb

- [CVE-2023-29193](https://insights.sbomify.com/CVE-2023-29193/): SpiceDB binding metrics port to untrusted networks and can leak command-line flags (high 8.7)
- [CVE-2022-21646](https://insights.sbomify.com/CVE-2022-21646/): Lookup operations do not take into account wildcards in SpiceDB (high 8.1)
- [CVE-2024-27101](https://insights.sbomify.com/CVE-2024-27101/): Integer overflow in chunking helper causes dispatching to miss elements or panic (high 7.3)
- [CVE-2026-40091](https://insights.sbomify.com/CVE-2026-40091/): SpiceDB: SPICEDB_DATASTORE_CONN_URI is leaked on startup logs (medium 6.0)
- [CVE-2025-49011](https://insights.sbomify.com/CVE-2025-49011/): SpiceDB checks involving relations with caveats can result in no permission when permission is expected (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46255 and fix it if it is affected.

What it is: CVE-2023-46255 is a medium-severity vulnerability in authzed spicedb, published on 31 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-46255 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/authzed/spicedb (Go): affected all versions; fixed in 1.27.0-rc1
- github.com/authzed/spicedb (Go): affected all versions; fixed in 1.27.0-rc1
- github.com/authzed/spicedb (Go): affected all versions; fixed in 1.27.0-rc1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-46255/ (Markdown: https://insights.sbomify.com/CVE-2023-46255/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-46255
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-46255
- OSV: https://osv.dev/vulnerability/CVE-2023-46255

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-46255/
Summaries are generated and may contain mistakes; the official description above is the record.