github.com/authzed/spicedb
Affected
- introduced
1.29.3, fixed1.49.1(semver)
Fixed versions
1.49.1
Fix
- Fixed version
1.49.1go get github.com/authzed/[email protected]
Advisory
Also known as: GO-2026-4465
LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic
Description
A malformed or tampered-with LookupResources Cursor token can cause a panic in the SpiceDB process if it fails to parse. If an attacker were able to make requests to a SpiceDB instance, they could affect its availability.
Reproduction
If one was to take a cursor from a LookupResources call, decode it according to the logic that SpiceDB uses, and modify the Sections field to include an invalid relationship string, the process will panic.
Impact
An attacker would need both the ability to create a gRPC connection to your SpiceDB instance and a valid token, or else the ability to pass a cursor token from outside your application through to your SpiceDB instance.
If an attacker had this ability, they could bring down SpiceDB instances, reducing the availability of SpiceDB and any service that depends on it.
Mechanism
The SpiceDB process does not validate the contents of this Sections component of the Cursor message. In affected versions, it uses a parsing function that calls panic if the value cannot be parsed as a relationship.
Fix
This issue was fixed in https://github.com/authzed/spicedb/pull/2878.
Remediations
optional_cursor field in LookupResources callsLow Basis: The source's own band: LOW
1.29.3, fixed 1.49.1 (semver)1.49.1
1.49.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