Froxlor
Froxlor: API Authentication bypasses 2FA Authentication
Froxlor is open source server administration software. Prior to 2.3.7, the API authentication path in lib/Froxlor/Api/FroxlorRPC.php and FroxlorRPC::validateAuth accepts an API key and secret for an administrator or customer account without checking type_2fa, validating a TOTP code, or invoking FroxlorTwoFactorAuth. The web interface requires a second factor for accounts with two-factor authentication enabled, but the API grants access after validating only the API credentials, expiration, API permission, and account status. An attacker who obtains an API key and secret for a protected account can call the available API functions without supplying the configured second factor, which can expose or modify customer data, domains, email and FTP accounts, databases, DNS records, and certificate material. This issue is fixed in version 2.3.7.
Affected versions and mitigation
From the CVE record, GitHub Security Advisories and the vendor's references.Affected
- <.3.7
- < 2.3.7
Fixed in 2.3.7
from GitHub Security Advisory GHSA-f9rx-7wf7-jr36
Mitigation
Upgrade froxlor/froxlor to 2.3.7 or later.
References
- Vendor advisory github.com/froxlor/froxlor/security/advisories…
- Patch github.com/froxlor/froxlor/commit/7fc21dc6f8d2…
- Release notes github.com/froxlor/froxlor/releases/tag/2.3.7
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.