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.
History

No history.

cve-icon MITRE Information

Status: PUBLISHED

Assigner: mitre

Published: 2020-07-15T20:27:39

Updated: 2020-07-15T20:27:39

Reserved: 2020-01-08T00:00:00


Link: CVE-2020-6165

JSON object: View

cve-icon NVD Information

Status : Analyzed

Published: 2020-07-15T21:15:13.583

Modified: 2020-07-23T14:22:48.577


Link: CVE-2020-6165

JSON object: View

cve-icon Redhat Information

No data.

CWE