MediumGHSA-ph62-fv59-vf9h
silverstripe/framework users inadvertently passing sensitive data to LoginAttempt
Published 27 May 2024 · Updated 2 Dec 2024
Affected packages
silverstripe/frameworkComposer
- Affected
- >=3.5.0-rc1 <3.5.6
- Fixed in
- 3.5.6
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.5.6silverstripe/frameworkComposer
- Affected
- >=3.6.0-rc1 <3.6.3
- Fixed in
- 3.6.3
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.6.3silverstripe/frameworkComposer
- Affected
- >=4.0.0-rc1 <4.0.1
- Fixed in
- 4.0.1
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^4.0.1Details
All user login attempts are logged in the database in the LoginAttempt table. However, this table contains information in plain text, and may possible contain sensitive information, such as user passwords mis-typed into the username field.
In order to address this a one-way hash is applied to the Email field before being stored.
Is GHSA-ph62-fv59-vf9h 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/3e2bcaa0b49277ff7f7004b265a7fa80d0b92e5c
- Linkgithub.com/silverstripe/silverstripe-framework/commit/c5d6eb816d4ac5e9fa3d8bc4bd82de95719eb22d
- Linkgithub.com/silverstripe/silverstripe-framework/commit/f1dd3d6f03eb1d94c29c495994a1da9176a758d9
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2017-009-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/ss-2017-009
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.