Skip to content

OpenFGA Authorization Bypass via tupleset wildcard

Moderate severity GitHub Reviewed Published Oct 24, 2022 in openfga/openfga • Updated Jun 27, 2023

Package

gomod github.com/openfga/openfga (Go)

Affected versions

<= 0.2.3

Patched versions

0.2.4

Description

Overview

During our internal security assessment, it was discovered that OpenFGA versions v0.2.3 and prior are vulnerable to authorization bypass under certain conditions.

Am I affected?

You are affected by this vulnerability if you are using openfga/openfga version v0.2.3 and you added a tuple with a wildcard (*) assigned to a tupleset relation (the right hand side of a ‘from’ statement).

How to fix that?

Upgrade to version v0.2.4.

Backward Compatibility

This update is not backward compatible with any authorization model that uses wildcard on a tupleset relation.

References

@SamyGhannad SamyGhannad published to openfga/openfga Oct 24, 2022
Published by the National Vulnerability Database Oct 25, 2022
Published to the GitHub Advisory Database Oct 25, 2022
Reviewed Oct 25, 2022
Last updated Jun 27, 2023

Severity

Moderate

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
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:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.212%
(60th percentile)

Weaknesses

CVE ID

CVE-2022-39341

GHSA ID

GHSA-vj4m-83m8-xpw5

Source code

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