Skip to content

Integer overflow in chunking helper causes dispatching to miss elements or panic

High severity GitHub Reviewed Published Mar 1, 2024 in authzed/spicedb

Package

gomod github.com/authzed/spicedb (Go)

Affected versions

< 1.29.2

Patched versions

1.29.2

Description

Any SpiceDB cluster with any schema where a resource being checked has more than 65535 relationships for the same resource and subject type is affected by this problem.

The issue may also lead to a panic rendering the server unavailable

The following API methods are affected:

Impact

Permission checks that are expected to be allowed are instead denied, and lookup subjects will return fewer subjects than expected.

Workarounds

There is no workaround other than making sure that the SpiceDB cluster does not have very wide relations, with the maximum value being the maximum value of an 16-bit unsigned integer

Remediations

  • AuthZed Dedicated customers: No action. AuthZed has upgraded all deployments.
  • AuthZed Serverless customers: No Action. AuthZed has upgraded all deployments.
  • AuthZed Enterprise customers: Upgrade to v1.29.2-hotfix-enterprise.v1.hotfix.v1
  • Open Source users: Upgrade to v1.29.2

References

@jzelinskie jzelinskie published to authzed/spicedb Mar 1, 2024
Published by the National Vulnerability Database Mar 1, 2024
Published to the GitHub Advisory Database Mar 1, 2024
Reviewed Mar 1, 2024

Severity

High

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
Changed
Confidentiality
None
Integrity
High
Availability
High

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:C/C:N/I:H/A:H

EPSS score

0.043%
(11th percentile)

Weaknesses

CVE ID

CVE-2024-27101

GHSA ID

GHSA-h3m7-rqc4-7h9p

Source code

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