Account access via unrestricted 2FA guessing
Published Jun 9, 2023 · Updated Jan 6, 2025
Improper 2FA attempt limiting in Froxlor before 2.0.20 allows remote attackers to brute-force a user's second factor. The 2fa_verify path checked each submitted code without incrementing loginfail_count or applying the existing login lockout threshold after failures. A correct primary credential and an account with 2FA enabled are required; guessing the second-factor code grants access as that account.
Summary
What happened
Improper 2FA attempt limiting in Froxlor before 2.0.20 allows remote attackers to brute-force a user's second factor. The 2fa_verify path checked each submitted code without incrementing loginfail_count or applying the existing login lockout threshold after failures. A correct primary credential and an account with 2FA enabled are required; guessing the second-factor code grants access as that account.
The record
- CVE
- CVE-2023-3173
- Published
- Jun 9, 2023
- Updated
- Jan 6, 2025
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-307, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2023CVE publishedPublication date reported by the CVE source.
- Jan 6, 2025Record 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 <2.0.20
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
- huntr.dev 2FA brute-force proof of conceptproof of concept · unverified
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