dbcve.org
OpenfgaApplication

CVE-2022-39352

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-08
Fix available
A fix is available. Upgrade to 0.2.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
OpenFGA is a high-performance authorization/permission engine inspired by Google Zanzibar. Versions prior to 0.2.5 are vulnerable to authorization bypass under certain conditions. You are affected by this vulnerability if you added a tuple with a wildcard (*) assigned to a tupleset relation (the right hand side of a ‘from’ statement). This issue has been patched in version v0.2.5. This update is not backward compatible with any authorization model that uses wildcard on a tupleset relation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenFGA versions prior to 0.2.5 contain an authorization bypass vulnerability where adding a tuple with a wildcard (*) to a tupleset relation (the right-hand side of a 'from' statement) allows unauthorized access to protected resources. This bypass occurs due to improper handling of wildcard expansion in authorization checks.

MitigationUpgrade to version v0.2.5 or later. Note: This update is NOT backward compatible with any authorization model that uses wildcards on tupleset relations—affected authorization models must be migrated before deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenfgaApplication
Affected:< 0.2.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed OpenFGA version
    Run 'openfga version' or inspect the Docker image tag. If running as a server, query the /metadata endpoint or check the startup logs for the version string.
    Affected if The version is less than 0.2.5 (e.g., 0.2.4, 0.2.3, etc.)
  2. Identify authorization models using wildcards on tupleset relations
    Query the OpenFGA API to list all authorization models in your store. For each model, examine the relation definitions and look for any 'from' (tupleset) clauses that reference relations where wildcard (*) expansion is possible.
    Affected if Any authorization model contains a relation with a 'from' clause pointing to a relation that can accept wildcard tuples
  3. Inspect existing tuples for wildcard patterns on tupleset relations
    Query the OpenFGA Read API to list all tuples in your store. Search for tuples where the object is a userset wildcard (format: 'namespace:id:*') and the relation matches a relation used as a tupleset in any authorization model.
    Affected if Any wildcard tuples exist where the relation serves as a tupleset (right-hand side of a 'from' statement) in your authorization model
  4. Verify wildcard usage on relations with inbound from clauses
    Cross-reference your tuple list with your authorization models. Identify any tuples with relation equal to a relation that other relations reference via 'from'. This is the vulnerable configuration pattern.
    Affected if Wildcard tuples exist on relations that are used as the 'from' source for other relations in authorization models

You are affected if running OpenFGA prior to version 0.2.5 AND your store contains authorization models with wildcard tuples on relations that are referenced by the 'from' clause of other relations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.2.5 or later
Fixed in 0.2.5
Interim mitigation

Upgrade to version v0.2.5 or later. Note: This update is NOT backward compatible with any authorization model that uses wildcards on tupleset relations—affected authorization models must be migrated before deployment.

Recommended fix High confidence

v0.2.5 or later

  1. 1. Stop the OpenFGA service
  2. 2. Backup your current OpenFGA installation and any authorization models that use wildcards on tupleset relations
  3. 3. Upgrade OpenFGA to version 0.2.5 or later
  4. 4. Review and update any authorization models that use wildcard (*) on a tupleset relation (the right-hand side of a 'from' statement) as these are not backward compatible
  5. 5. Restart the OpenFGA service
  6. 6. Verify the authorization is working correctly and test for the bypass condition
Caveat This update is not backward compatible with any authorization model that uses wildcard on a tupleset relation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openfga Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39352 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data