CVE-2020-6165
Description
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.
How to fix
- silverstripe silverstripe3.2.4, 3.3.0, 4.5.3 or later
- silverstripe/recipe-cms4.5.3 or later
- silverstripe/graphql3.2.4 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| silverstripe silverstripe | 3.2.0 ≤ v < 3.2.4, 3.2.5 ≤ v < 3.3.0, 4.5.0 ≤ v < 4.5.3 | 3.2.4, 3.3.0, 4.5.3 |
| silverstripe/recipe-cmsPackagist | 4.5.0 ≤ v < 4.5.3 | 4.5.3 |
| silverstripe/graphqlPackagist | 3.2.0 ≤ v < 3.2.4 | 3.2.4 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.