dbcve.org
FidesApplication · Ethyca

CVE-2024-52008

HIGH · 8.8 CVSS v3.1 Published 2024-11-26
Fix available
A fix is available. Upgrade to 2.50.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Fides is an open-source privacy engineering platform. The user invite acceptance API endpoint lacks server-side password policy enforcement, allowing users to set arbitrarily weak passwords by bypassing client-side validation. While the UI enforces password complexity requirements, direct API calls can circumvent these checks, enabling the creation of accounts with passwords as short as a single character. When an email messaging provider is enabled and a new user account is created in the system, an invite email containing a special link is sent to the new user's email address. This link directs the new user to a page where they can set their initial password. While the user interface implements password complexity checks, these validations are only performed client-side. The underlying `/api/v1/user/accept-invite` API endpoint does not implement the same password policy validations. This vulnerability allows an invited user to set an extremely weak password for their own account during the initial account setup process. Therefore that specific user's account can be compromised easily by an attacker guessing or brute forcing the password. The vulnerability has been patched in Fides version `2.50.0`. Users are advised to upgrade to this version or later to secure their systems against this threat. There are no known workarounds for this vulnerability.

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

The `/api/v1/user/accept-invite` endpoint in Fides lacks server-side password policy enforcement. While the UI enforces password complexity, direct API calls bypass these checks, allowing passwords as weak as a single character during initial account setup.

MitigationUpgrade to Fides version 2.50.0 or later to receive the patch that adds server-side password validation to the invite acceptance endpoint.

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
FidesApplication
Affected:< 2.50.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Fides version
    Run 'fides --version' or check the version in your deployment configuration, Docker image tag, or Helm chart values. Compare this to the affected range: versions below 2.50.0 are vulnerable.
    Affected if The installed version is lower than 2.50.0 (e.g., 2.49.0, 2.48.0, etc.)
  2. Verify API endpoint accessibility
    Confirm that the Fides API server is running and network-accessible. The vulnerable endpoint is /api/v1/user/accept-invite.
    Affected if The API server is exposed and reachable over the network.
  3. Identify if invite-based user creation is in use
    Determine whether your Fides deployment uses the invite/acceptance flow for initial user creation rather than admin-created users. Check your user management settings or logs for invite-related activity.
    Affected if Your deployment relies on the invite acceptance flow for setting up user accounts.

You are affected if your Fides version is below 2.50.0 AND the /api/v1/user/accept-invite endpoint is accessible AND your deployment uses the invite acceptance flow for user creation.

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 2.50.0 or later
Fixed in 2.50.0
Interim mitigation

Upgrade to Fides version 2.50.0 or later to receive the patch that adds server-side password validation to the invite acceptance endpoint.

Recommended fix High confidence

2.50.0 or later

  1. Download Fides version 2.50.0 or later from the official repository
  2. Follow the standard Fides upgrade procedure for your deployment method (e.g., pip install, Docker, or Helm)
  3. Restart the Fides services after upgrading
  4. Verify the upgrade by checking the installed version matches or exceeds 2.50.0
  5. Test the /api/v1/user/accept-invite endpoint to confirm server-side password validation is now enforced

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

Fix this in Fides Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52008 — 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-2024-52008 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