MediumGHSA-vj2j-6g3w-4662
Silverstripe Missing CSRF protection in login form
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
LoginForm calls disableSecurityToken(), which causes a "shared host domain" vulnerability: http://stackoverflow.com/a/15350123.
Is GHSA-vj2j-6g3w-4662 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/a6bd22ab2f3b11a054d20be13306a19089510989
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-006-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkstackoverflow.com/questions/6412813/do-login-forms-need-tokens-against-csrf-attacks/15350123#15350123
- Linkwww.silverstripe.org/download/security-releases/ss-2016-006
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.