Skip to content

GHSA-2hm9-h873-pgqh CVE-2023-43645 GO-2023-2084

OpenFGA Vulnerable to DoS from circular relationship definitions

Medium Go
Severity
5.9 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.94%
Chance of exploitation in the next 30 days. Higher than 60.86% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop')
Fix
1.3.2
Upgrade github.com/openfga/openfga to this version or later

Description

Overview

OpenFGA is vulnerable to a DoS attack when certain Check calls are executed against authorization models that contain circular relationship definitions. When the call is made, it's possible for the server to exhaust resources and die.

Am I Affected?

Yes, if your store contains an authorization model that allows circular relationships. For example, with this model:

model
  schema 1.1

type user

type group
  relations
    define memberA: [user] or memberB or memberC or memberD or memberE
    define memberB: [user] or memberA or memberC or memberD or memberE
    define memberC: [user] or memberA or memberB or memberD or memberE
    define memberD: [user] or memberA or memberB or memberC or memberE
    define memberE: [user] or memberA or memberB or memberC or memberD

This Check: (user:anne, memberA, group:X) can exhaust memory in the server.

Fix

Upgrade to v1.3.2 and update any offending models.

[BREAKING] If your model contained cycles or a relation definition that has the relation itself in its evaluation path, then Checks and queries that require evaluation will no longer be evaluated on v1.3.2+ and will return errors instead. You will need to update your models to remove the cycles.

Affected versions

Go

PackageVulnerableFixed in
github.com/openfga/openfga
< 1.3.2
1.3.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/openfga/openfga Go → 1.3.2

go
go get github.com/openfga/openfga@v1.3.2 && go mod tidy

Severity breakdown

CVSS 3.1 5.9

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

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

Weakness

CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-g3pg-frfm-pr2m
OpenFGA: ListUsers returns a deliberately-excluded user when a `but not` exclusion under a type-bound wildcard is intersected (`and`) with another relation that also grants that user
Medium Also affects github.com/openfga/openfga
GHSA-hcxc-wf8j-23hv
OpenFGA: OIDC audience validation skipped when --authn-oidc-audience is unset
High Also affects github.com/openfga/openfga
GHSA-cf98-j28v-49v6
OpenFGA Improper Policy Enforcement
Medium Also affects github.com/openfga/openfga
GHSA-8396-jffm-qx4w
OpenFGA has cache-key delimiter injection in shared-iterator and v2 iterator that caches enables intra-store authorization-decision poisoning
Medium Also affects github.com/openfga/openfga
GHSA-57j5-qwp2-vqp6
OpenFGA has Improper Policy Enforcement
Medium Also affects github.com/openfga/openfga
GHSA-68m9-983m-f3v5
OpenFGA: Unauthenticated playground endpoint discloses preshared API key in HTML response
Medium Also affects github.com/openfga/openfga
GHSA-jwvj-g8pc-cx45
OpenFGA's BatchCheck within-request deduplication produces incorrect authorization decisions via list-value cache-key collision
High Also affects github.com/openfga/openfga
GHSA-h6c8-cww8-35hf
OpenFGA has an Authorization Bypass through cached keys
Critical Also affects github.com/openfga/openfga
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor