CVE-2020-6165
Silverstripe has Incorrect Default Permissions
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 CVE-2020-6165
To remediate CVE-2020-6165, upgrade the affected package to a fixed version below.
- —upgrade to 3.2.4 or later
- —upgrade to 3.2.4 or later
- —upgrade to 4.5.3 or later
Is CVE-2020-6165 being exploited?
Low — EPSS is 0.2%, meaning exploitation activity has not been observed at scale.
Affected packages (3)
- >= 3.2.0, < 3.2.4, >= 3.2.5, < 3.3.0, >= 4.5.0, < 4.5.3
- >= 3.2.0, < 3.2.4
- >= 4.5.0, < 4.5.3
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 3.1 | MEDIUM5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |