MFA bypass in oauth flow in Firefly III
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| firefly-iii | firefly-iii | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Firefly-iii | Firefly Iii | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-1910 | 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. |
Github GHSA |
GHSA-4gm4-c4mh-4p7w | Firefly III has a MFA bypass in oauth flow |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.594% probability within 30 days)
No history.