Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Silverstripe | Silverstripe | >= 3.2.0, < 3.2.4 |
Related Weaknesses (CWE)
References
- https://www.silverstripe.org/download/security-releases/CVE-2020-6165Vendor Advisory
- https://www.silverstripe.org/download/security-releases/CVE-2020-6165Vendor Advisory
FAQ
What is CVE-2020-6165?
CVE-2020-6165 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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...
How severe is CVE-2020-6165?
CVE-2020-6165 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2020-6165?
Check the references section above for vendor advisories and patch information. Affected products include: Silverstripe Silverstripe.