Skip to content

SpiceDB: LookupSubjects may return partial results if a specific kind of relation is used

Low severity GitHub Reviewed Published Apr 10, 2024 in authzed/spicedb • Updated Apr 11, 2024

Package

gomod github.com/authzed/spicedb (Go)

Affected versions

< 1.30.1

Patched versions

1.30.1

Description

Background

Use of a relation of the form: relation folder: folder | folder#parent with an arrow such as folder->view can cause LookupSubjects to only return the subjects found under subjects for either folder or folder#parent.

This bug only manifests if the same subject type is used multiple types in a relation, relationships exist for both subject types and an arrow is used over the relation.

Impact

Any user making a negative authorization decision based on the results of a LookupSubjects request with version before v1.30.1 is affected.

Workarounds

Avoid using LookupSubjects for negative authorization decisions and/or avoid using the broken schema.

References

@ecordell ecordell published to authzed/spicedb Apr 10, 2024
Published to the GitHub Advisory Database Apr 10, 2024
Reviewed Apr 10, 2024
Published by the National Vulnerability Database Apr 10, 2024
Last updated Apr 11, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-32001

GHSA ID

GHSA-j85q-46hg-36p2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.