dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-37893

MEDIUM · 5.9 CVSS v3.1 Published 2024-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
Firefly III is a free and open source personal finance manager. In affected versions an MFA bypass in the Firefly III OAuth flow may allow malicious users to bypass the MFA-check. This allows malicious users to use password spraying to gain access to Firefly III data using passwords stolen from other sources. As OAuth applications are easily enumerable using an incrementing id, an attacker could try sign an OAuth application up to a users profile quite easily if they have created one. The attacker would also need to know the victims username and password. This problem has been patched in Firefly III v6.1.17 and up. Users are advised to upgrade. Users unable to upgrade should Use a unique password for their Firefly III instance and store their password securely, i.e. in a password manager.

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

Firefly III versions before v6.1.17 contain an MFA bypass vulnerability in the OAuth authentication flow. Attackers who have obtained a victim's username and password can bypass MFA protection by manipulating OAuth application enrollment, which uses easily enumerable incrementing IDs to attach a malicious OAuth application to a user's profile.

MitigationUpgrade to Firefly III v6.1.17 or later to receive the patch. If immediate upgrade is not feasible, ensure unique passwords are used for the Firefly III instance and stored securely in a password manager to mitigate password-spraying attacks.

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

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify installed Firefly III version
    Access the Firefly III admin interface and navigate to the System Administration or About page, or check the docker container/CHANGELOG.md file for the version number
    Affected if the installed version is earlier than v6.1.17
  2. Verify OAuth application functionality is enabled
    Inspect the Firefly III configuration file (usually .env) or database for oauth_clients table entries; check if OAUTH_ENABLED or similar OAuth-related settings are present and set to true
    Affected if OAuth functionality is enabled and the version is below v6.1.17
  3. Review OAuth applications registered to user accounts
    Query the database for oauth_clients table or use admin API endpoints to list OAuth applications; examine the client_id, redirect_uri, and user_id columns for unexpected or unauthorized entries
    Affected if any OAuth applications exist that were not created by the account owner, especially with suspicious redirect URIs
  4. Audit recent OAuth authorization grants
    Check the database oauth_auth_codes or oauth_access_tokens tables for recent authorization entries; look for timestamps that correlate with login events where MFA was expected but not enforced
    Affected if oauth_auth_codes or access tokens exist for users without corresponding MFA-verified sessions in the same timeframe

A user is affected if Firefly III version is below v6.1.17 and OAuth functionality is enabled, with any unauthorized OAuth applications attached to user accounts indicating exploitation of this MFA bypass vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Firefly III v6.1.17 or later to receive the patch. If immediate upgrade is not feasible, ensure unique passwords are used for the Firefly III instance and stored securely in a password manager to mitigate password-spraying attacks.

Recommended fix High confidence

Firefly III v6.1.17

  1. Upgrade Firefly III to version 6.1.17 or later
  2. After upgrade, verify MFA is functioning correctly by testing the OAuth flow
  3. As an additional security measure, ensure you use a unique password for your Firefly III instance stored in a password manager

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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