Skip to content

Firefly III has a MFA bypass in oauth flow

Moderate severity GitHub Reviewed Published Jun 17, 2024 in firefly-iii/firefly-iii • Updated Jun 17, 2024

Package

composer grumpydictator/firefly-iii (Composer)

Affected versions

< 6.1.17

Patched versions

6.1.17

Description

Impact

A 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 your 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.

Patches

Problem has been patched in Firefly III v6.1.17 and up.

Workarounds

  • Use a unique password for your Firefly III instance,
  • Store your password securely, i.e. in a password manager or in your head.

References

References

@JC5 JC5 published to firefly-iii/firefly-iii Jun 17, 2024
Published by the National Vulnerability Database Jun 17, 2024
Published to the GitHub Advisory Database Jun 17, 2024
Reviewed Jun 17, 2024
Last updated Jun 17, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.045%
(16th percentile)

CVE ID

CVE-2024-37893

GHSA ID

GHSA-4gm4-c4mh-4p7w

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.