GHSA-52cx-hpc5-cxwc json
silverstripe/framework missing ACL on reports
published 2y ago modified last yr.
- cvss
- 4.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist silverstripe/framework 3.1.20, 3.2.5, 3.3.3, 3.4.1
Is GHSA-52cx-hpc5-cxwc in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | silverstripe/framework | >=3.1.19-rc1, <3.1.20 >=3.2.4-rc1, <3.2.5 >=3.3.2-rc1, <3.3.3 >=3.4.0-rc1, <3.4.1 |
3.1.20 3.2.5 3.3.3 3.4.1 |
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
Sources
- GitHub Advisory GHSA-52cx-hpc5-cxwc
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.