EUVD-2024-1910 · Published Jun 17, 2024
Firefly III has a MFA bypass in oauth flow
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
Technologies
Weaknesses
CVSS scores
- v3.15.9
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
MITRE ATT&CK
InferredWhere this vulnerability fits in an attack
References
- https://github.com/firefly-iii/firefly-iii/security/advisories/GHSA-4gm4-c4mh-4p7w
- https://owasp.org/www-community/attacks/Password_Spraying_Attack
- https://www.menlosecurity.com/what-is/highly-evasive-adaptive-threats-heat/mfa-bypass
- https://nvd.nist.gov/vuln/detail/CVE-2024-37893
- https://github.com/firefly-iii/firefly-iii
Potentially impacted assets
See if this affects your attack surface




