CyberRota Analysis
AI-GeneratedThe vulnerability affects Filament's multi-factor authentication (MFA) implementation, allowing an attacker to reuse a previously issued app-based MFA code within a specific time window, even after a newer code has been generated by the legitimate user. This flaw can be exploited if an attacker has obtained both the target account's password and a valid MFA code, potentially compromising account security for approximately four minutes. Organizations using affected versions of Filament should prioritize updating to versions 4.12.6 or 5.7.6 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.12.6 and 5.7.6, packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php uses AppAuthentication::verifyCode() with a used-code cache key derived from both the app authentication secret and the submitted TOTP code. This isolates the newest accepted timestep by code instead of by secret, allowing a previously issued app-based MFA code to be accepted after a newer code has already been used. Reuse of the exact same code was already prevented, but another code inside the accepted time window remained usable. An attacker who obtains the target account's password and one app-based MFA code can use that code for the remainder of the configured window, which is approximately four minutes with the default settings, even after the legitimate account holder logs in with a newer code. Email-based MFA is not affected. This issue is fixed in versions 4.12.6 and 5.7.6.