Advisory

GHSA-grjv-gjgr-66g2

Also known as: CVE-2024-38361, GO-2024-2939

Summary

SpiceDB exclusions can result in no permission returned when permission expected

Details

Background

Use of an exclusion under an arrow that has multiple resources may resolve to NO_PERMISSION when permission is expected.

For example, given this schema:

definition user {}

definition folder {
  relation member: user
  relation banned: user
  permission view = member - banned
}

definition resource {
  relation folder: folder
  permission view = folder->view
}

If the resource exists under *multiple* folders and the user has access to view more than a single folder, SpiceDB may report the user does not have access due to a failure in the exclusion dispatcher to request that *all* the folders in which the user is a member be returned

Impact

Permission is returned as NO_PERMISSION when PERMISSION is expected on the CheckPermission API.

Workarounds

None

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-06-20 16:24 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/authzed/spicedb

Go · All systems

Affected

  • introduced 0, fixed 1.33.1 (semver)

Fixed versions

1.33.1

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences