Описание
Filament: Multi-factor authentication (app) codes can still be used after a newer code has been used
A flaw in the handling of one-time codes for app-based multi-factor authentication allows a previously issued code to be used after a newer code has already been accepted. This issue does not affect email-based MFA. Submitting the exact same code twice was already prevented, but any other code within the accepted time window was not.
If an attacker gains access to both the user's password and a single one-time code, that code stays usable for the remainder of its time window, which is around four minutes on the default settings, including after the legitimate user has already logged in with a newer code.
Ссылки
- https://github.com/filamentphp/filament/security/advisories/GHSA-r3j6-gpjw-qfjr
- https://github.com/filamentphp/filament/pull/20335
- https://github.com/filamentphp/filament/commit/b6bde8572bcac75d4f5b4ec892ba7b9e91e0ab4d
- https://github.com/filamentphp/filament/releases/tag/v4.12.6
- https://github.com/filamentphp/filament/releases/tag/v5.7.6
Пакеты
filament/filament
>= 4.0.0, < 4.12.6
4.12.6
filament/filament
>= 5.0.0, < 5.7.6
5.7.6
Связанные уязвимости
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.
Уязвимость метода AppAuthentication::verifyCode() файла packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php набора компонентов полного стека для ускоренной разработки Filament PHP-фреймворка Laravel, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации