Skip to content

SpiceDB calls to LookupResources using LookupResources2 with caveats may return context is missing when it is not

Low severity GitHub Reviewed Published Oct 14, 2024 in authzed/spicedb • Updated Oct 14, 2024

Package

gomod github.com/authzed/spicedb (Go)

Affected versions

>= 1.35.0, < 1.37.1

Patched versions

1.37.1

Description

Impact

Clients that have enabled LookupResources2 and have caveats in the evaluation path for their requests can return a permissionship of CONDITIONAL with context marked as missing, even then the context was supplied.

LookupResources2 is the new default in SpiceDB 1.37.0 and has been opt-in since SpiceDB 1.35.0

Patches

The bug will be released as part of SpiceDB 1.37.1

Workarounds

Disable LookupResources2 via the --enable-experimental-lookup-resources flag by setting it to false

--enable-experimental-lookup-resources=false

References

@vroldanbet vroldanbet published to authzed/spicedb Oct 14, 2024
Published to the GitHub Advisory Database Oct 14, 2024
Reviewed Oct 14, 2024
Published by the National Vulnerability Database Oct 14, 2024
Last updated Oct 14, 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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
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:R/S:U/C:L/I:N/A:N

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2024-48909

GHSA ID

GHSA-3c32-4hq9-6wgj

Source code

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