Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-f4mm-2r69-mg5f: OpenFGA Authorization Bypass

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 or prior, and your model has a relation defined as a tupleset (the right hand side of a ‘from’ statement) that involves anything other than a direct relationship (e.g. ‘as self’)

How to fix that?

Upgrade to version v0.2.4.

Backward Compatibility

This update is not backward compatible. Any model involving rewritten tupleset relations will no longer be acceptable and has to be modified.

ghsa
#vulnerability#git#auth

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 or prior, and your model has a relation defined as a tupleset (the right hand side of a ‘from’ statement) that involves anything other than a direct relationship (e.g. ‘as self’)

How to fix that?

Upgrade to version v0.2.4.

Backward Compatibility

This update is not backward compatible.
Any model involving rewritten tupleset relations will no longer be acceptable and has to be modified.

References

  • GHSA-f4mm-2r69-mg5f
  • https://nvd.nist.gov/vuln/detail/CVE-2022-39342
  • openfga/openfga@c8db1ee
  • https://github.com/openfga/openfga/releases/tag/v0.2.4

Related news

CVE-2022-39342: OpenFGA Authorization Bypass

OpenFGA is an authorization/permission engine. Versions prior to version 0.2.4 are vulnerable to authorization bypass under certain conditions. Users whose model has a relation defined as a tupleset (the right hand side of a ‘from’ statement) that involves anything other than a direct relationship (e.g. ‘as self’) are vulnerable. Version 0.2.4 contains a patch for this issue.