MediumGHSA-52cx-hpc5-cxwc

silverstripe/framework missing ACL on reports

Published 27 May 2024 · Updated 2 Dec 2024

Affected packages

silverstripe/frameworkComposer

Affected: >=3.1.19-rc1 <3.1.20
Fixed in: 3.1.20

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.1.20

silverstripe/frameworkComposer

Affected: >=3.2.4-rc1 <3.2.5
Fixed in: 3.2.5

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.2.5

silverstripe/frameworkComposer

Affected: >=3.3.2-rc1 <3.3.3
Fixed in: 3.3.3

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.3.3

silverstripe/frameworkComposer

Affected: >=3.4.0-rc1 <3.4.1
Fixed in: 3.4.1

Update to the fixed version for your release line, for example:composer require silverstripe/framework:^3.4.1

Details

The SS_Report, and the reports CMS section only checks canView() when listing the reports that can be viewed by the current user.

It does not (and should) perform canView checks when the report is actually viewed, so if you know the URL to a report and can otherwise access the Reports section of the CMS, you can view any report.

Is GHSA-52cx-hpc5-cxwc 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 signup Or connect GitHub to scan every repo

References

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