CVE-2024-42473
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 · uneditedOpenFGA is an authorization/permission engine. OpenFGA v1.5.7 and v1.5.8 are vulnerable to authorization bypass when calling Check API with a model that uses `but not` and `from` expressions and a userset. Users should downgrade to v1.5.6 as soon as possible. This downgrade is backward compatible. As of time of publication, a patch is not available but OpenFGA's maintainers are planning a patch for inclusion in a future release.
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 · moderate confidenceOpenFGA v1.5.7 and v1.5.8 contain an authorization bypass vulnerability in the Check API. When authorization models use `but not` and `from` expressions combined with a userset, the Check API incorrectly grants access, allowing unauthorized users to access resources they should not have permission to view.
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= 1.5.7= 1.5.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check OpenFGA versionRun 'openfga version' from the CLI, or query the /healthz endpoint which returns version info, or inspect the running container image tagAffected if The installed version is 1.5.7 or 1.5.8
-
Identify authorization models in useQuery the OpenFGA API: GET /v1/authorization-models to list stored models, or check your deployment's model definitions stored in the databaseAffected if Any authorization model is stored or deployed in the system
-
Examine models for vulnerable DSL patternReview each authorization model's DSL definition for the presence of 'but not' and 'from' expressions used together within a relationship definition that references a userset (e.g., 'but not from <userset>')Affected if The model contains 'but not' and 'from' expressions combined with a userset in any relation definition
-
Verify Check API is accessibleConfirm the Check API endpoint (POST /v1/claims/check) is enabled and reachable in your deploymentAffected if The Check API is exposed and used for authorization decisions
-
Test for authorization bypassSubmit a Check API request using a subject that should be denied by a 'but not from' rule - compare the response against expected permission logicAffected if The Check API returns 'allowed: true' for requests that should be denied according to the 'but not from' logic in your model
You are affected if running OpenFGA version 1.5.7 or 1.5.8 AND your authorization models contain 'but not' expressions combined with 'from' and a userset, which causes the Check API to incorrectly grant access.
Generated from the published advisory. Verify against your own configuration.
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 · scopedDowngrade to v1.5.6 immediately as no patch is available yet. This version is backward compatible with existing deployments.
OpenFGA v1.5.6
- Stop the OpenFGA service
- Update or reinstall OpenFGA to version 1.5.6
- Restart the OpenFGA service
- Verify the service is running and the Check API functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-42473 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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