LowGHSA-vh7q-j8p5-2h4h
silverstripe/framework sends passwords back to browsers under some circumstances
Published 27 May 2024 · Updated 2 Dec 2024
Affected packages
silverstripe/frameworkComposer
- Affected
- >=3.5.5-rc1 <3.7.0
- Fixed in
- 3.7.0
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.7.0silverstripe/frameworkComposer
- Affected
- >=4.0.3-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
Under some circumstances a form may populate a PasswordField with submitted data, reflecting submitted data back to a user. The user will only see their own submissions for password data, which is not considered best practice. We are not aware of data leaks to other users, devices or sessions.
Is GHSA-vh7q-j8p5-2h4h 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/c28f411abd4837cdd9dbf87c4457976e678131cb
- Linkgithub.com/silverstripe/silverstripe-framework/commit/f688bcb1a370e41df1b573a24fa3994b3895bacf
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2018-013-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/ss-2018-013
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.