Silverstripe has Incorrect Default Permissions
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| silverstripe/recipe-cms Packagist |
|
|
| silverstripe/graphql Packagist |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| silverstripe/recipe-cms Packagist |
|
|
| silverstripe/graphql Packagist |
|
|
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.
From the CVE record · mitre
The silverstripe/graphql permission check can include records in limited result sets, such as paginated lists, that a user should not be allowed to read. Authenticated users, including users with limited permissions, can read affected records through the access-protected admin/graphql endpoint. Unauthenticated requests may also exploit this issue if a custom GraphQL endpoint has been configured; the issue does not allow records to be changed.
Check installations using silverstripe/recipe-cms versions >=4.5.0 <4.5.3 or silverstripe/graphql versions >=3.2.0 <3.2.4.