MediumGHSA-crr3-h4m8-7f56
silverstripe/framework vulnerable to member disclosure in login form
Published 27 May 2024 · Updated 2 Dec 2024
Affected packages
silverstripe/frameworkComposer
- Affected
- >=4.0.0-rc1 <4.0.4
- Fixed in
- 4.0.4
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^4.0.4silverstripe/frameworkComposer
- Affected
- >=4.1.0-rc1 <4.1.1
- Fixed in
- 4.1.1
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^4.1.1Details
There is a user ID enumeration vulnerability in our brute force error messages.
- Users that don't exist in will never get a locked out message
- Users that do exist, will get a locked out message
This means an attacker can infer or confirm user details that exist in the member table.
This issue has been resolved by ensuring that login attempt logging and lockout process works equivalently for non-existent users as it does for existant users.
This is a regression of SS-2017-002.
Is GHSA-crr3-h4m8-7f56 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/5887201dd578a5b9779c33a182153d2ce973ab41
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2018-010-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/ss-2018-010
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.