MediumGHSA-q9ff-3q93-fm8mCVE-2019-19326
SilverStripe Web Cache Poisoning through HTTPRequestBuilder
Published 24 May 2022 · Updated 22 May 2024
Affected packages
silverstripe/frameworkComposer
- Affected
- >=4.0.0 <4.4.7
- Fixed in
- 4.4.7
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^4.4.7silverstripe/frameworkComposer
- Affected
- >=4.5.0 <4.5.4
- Fixed in
- 4.5.4
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^4.5.4silverstripe/frameworkComposer
- Affected
- >=3.0.0 <3.7.5
- Fixed in
- 3.7.5
Update to the fixed version for your release line, for example:
composer require silverstripe/framework:^3.7.5Details
SilverStripe through 4.4.4 allows Web Cache Poisoning through HTTPRequestBuilder.
Is GHSA-q9ff-3q93-fm8m 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
- Advisorynvd.nist.gov/vuln/detail/CVE-2019-19326
- Linkgithub.com/silverstripe/silverstripe-framework/commit/107706c12cd9cf4d1b8b96b6a6e223633209d851
- Linkgithub.com/silverstripe/silverstripe-framework/commit/8518987cbd1eaca71b65dd4a4b35591db941509a
- Linkgithub.com/silverstripe/silverstripe-framework/commit/98926e4e6c26d1d43bb1faf516d15bdb2739556e
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/CVE-2019-19326.yaml
- Packagegithub.com/silverstripe/silverstripe-framework
- Linkwww.silverstripe.org/download/security-releases/CVE-2019-19326
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.