HighGHSA-4qx8-j9vh-2628
silverstripe/framework's User-Agent header not correctly invalidating user session
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.3Details
A security protection device in Session designed to protect session hijacking was not correctly functioning. This function intended to protect user sessions by detecting changes in the User-Agent header, but modifications to this header were not correctly invalidating the user session.
Is GHSA-4qx8-j9vh-2628 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/44de03da0147e6094b02602b7b73d5b1a1306d78
- Linkgithub.com/silverstripe/silverstripe-framework/commit/d47667bb0768841e4b305fa95d5a4e2ba232c4ad
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2017-006-1.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/ss-2017-006
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.