CVE-2020-6165
CVE-2020-6165
This page contains facts from public vulnerability sources. Check the original advisory before updating.
SilverStripe 4.5.0 allows attackers to read certain records that should not have been placed into a result set. This affects silverstripe/recipe-cms. The automatic permission-checking mechanism in the silverstripe/graphql module does not provide complete protection against lists that are limited (e.g., through pagination), resulting in records that should have failed a permission check being added to the final result set. GraphQL endpoints are configured by default (e.g., for assets), but the admin/graphql endpoint is access protected by default. This limits the vulnerability to all authenticated users, including those with limited permissions (e.g., where viewing records exposed through admin/graphql requires administrator permissions). However, if custom GraphQL endpoints have been configured for a specific implementation (usually under /graphql), this vulnerability could also be exploited through unauthenticated requests. This vulnerability only applies to reading records; it does not allow unauthorised changing of records.
CVSS 5.3 · Medium · EPSS 1.1% · Fix available
- Published
- Updated
Stack: php
Affected products and versions
n/a
- Versions
- n/a: Affected
No fix published
silverstripe/recipe-cms Packagist
- Versions
- 4.5.0
- 4.5.1
- 4.5.2
- Affected ranges
- ECOSYSTEM: ≥ 4.5.0, < 4.5.3
Update to 4.5.3
silverstripe/graphql Packagist
- Versions
- 3.2.0
- 3.2.1
- 3.2.2
- 3.2.3
- Affected ranges
- ECOSYSTEM: ≥ 3.2.0, < 3.2.4
Update to 3.2.4