vulnerability / NVI-00018259 / Revision 1
SpiceDB: Caveat structures with nested lists can result in improper cache reuse
GitHub lists this reviewed advisory for github.com/authzed/spicedb. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
github.com/authzed/spicedb
source listed>= 1.15.0, < 1.52.0
### Impact Users are impacted if: - They have a caveat structure with a nested list, e.g.: ```zed caveat shape(x list) { x == [["a"], "b"] } ``` - Their system exercises that caveat with either CheckBulkPermission or else LookupResources running with the `--experimental-lookup-resources-version` flag set to `lr3`, implying they are using the experimental version 3 of `LookupResources` - An attacker can cause the system to craft a request to SpiceDB where either: 1. It's a `CheckBulk` request where there are two check items that are identical except for their combined caveat context, and one of the caveat contexts evaluates positively and the other evaluates negatively 2. It's a `LookupResources` request where two resources have the same evaluation contents except for their caveat context, and one would evaluate positively and the other would evaluate negatively If all of the above are true, it would be possible for SpiceDB to errone
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-mqcf-gqvg-rmhm ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.