Two-factor authentication disablement via tokenless GET request
Published Dec 4, 2021 · Updated Aug 3, 2024
Cross-site request forgery in Firefly III before 5.6.6 allows remote attackers to disable a target user's two-factor authentication. The profile view renders the profile.delete-code action as a GET link without a CSRF token, so a browser can submit the state-changing request cross-origin. Exploitation requires a signed-in user with two-factor authentication enabled to visit attacker-controlled content; the result is removal of that account protection.
Summary
What happened
Cross-site request forgery in Firefly III before 5.6.6 allows remote attackers to disable a target user's two-factor authentication. The profile view renders the profile.delete-code action as a GET link without a CSRF token, so a browser can submit the state-changing request cross-origin. Exploitation requires a signed-in user with two-factor authentication enabled to visit attacker-controlled content; the result is removal of that account protection.
The record
- CVE
- CVE-2021-4005
- Published
- Dec 4, 2021
- Updated
- Aug 3, 2024
- Vendor
- Firefly III
- Product
- Firefly III
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <5.6.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo