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.
References
Link | Resource |
---|---|
https://www.silverstripe.org/download/security-releases/CVE-2020-6165 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2020-07-15 21:15
Updated : 2024-02-28 17:47
NVD link : CVE-2020-6165
Mitre link : CVE-2020-6165
CVE.ORG link : CVE-2020-6165
JSON object : View
Products Affected
silverstripe
- silverstripe
CWE
CWE-276
Incorrect Default Permissions