CriticalGHSA-8v6m-7f5v-hhx6
Silverstripe Brute force bypass on default admin
Published 23 May 2024 · Updated 28 Nov 2024
Affected packages
silverstripe/frameworkComposer
- Affected
- >=3.1.18 <3.1.19
- Fixed in
- 3.1.19
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.1.19silverstripe/frameworkComposer
- Affected
- >=3.2.3 <3.2.4
- Fixed in
- 3.2.4
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.2.4silverstripe/frameworkComposer
- Affected
- >=3.3.1 <3.3.2
- Fixed in
- 3.3.2
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.3.2Details
Default Administrator accounts were not subject to the same brute force protection afforded to other Member accounts. Failed login counts were not logged for default admins resulting in unlimited attempts on the default admin username and password.
Is GHSA-8v6m-7f5v-hhx6 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected silverstripe/framework, and gives you the command that fixes it.
References
- Linkgithub.com/silverstripe/silverstripe-framework/commit/f32c893546340c8c279fd1ab6d4269e9d6539bc2
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-005-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/ss-2016-005
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.