MediumGHSA-jvx5-rm6q-gx7pCVE-2019-12245

Lack of access control on upoaded files

Published 12 Nov 2019 · Updated 16 Feb 2024

Affected packages

silverstripe/frameworkComposer
Affected
<3.6.8
Fixed in
3.6.8
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.6.8
silverstripe/frameworkComposer
Affected
>=3.7.0 <3.7.4
Fixed in
3.7.4
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.7.4
silverstripe/frameworkComposer
Affected
>=4.0.0 <4.3.6
Fixed in
4.3.6
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.3.6
silverstripe/frameworkComposer
Affected
>=4.4.0 <4.4.4
Fixed in
4.4.4
Update to the fixed version for your release line, for example:composer require silverstripe/framework:^4.4.4
silverstripe/assetsComposer
Affected
>=1.0.0 <1.3.5
Fixed in
1.3.5
Update to the fixed version for your release line, for example:composer require silverstripe/assets:^1.3.5
silverstripe/assetsComposer
Affected
>=1.4.0 <1.4.4
Fixed in
1.4.4
Update to the fixed version for your release line, for example:composer require silverstripe/assets:^1.4.4

Details

SilverStripe through 4.3.3 has incorrect access control for protected files uploaded via Upload::loadIntoFile(). An attacker may be able to guess a filename in silverstripe/assets via the AssetControlExtension.

Is GHSA-jvx5-rm6q-gx7p 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.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.