{"id":"BIT-silverstripe-2020-6165","details":"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.","aliases":["CVE-2020-6165","GHSA-589q-75r3-mfq4"],"modified":"2024-03-06T11:25:28.861Z","published":"2024-03-06T11:06:12.375Z","database_specific":{"cpes":["cpe:2.3:a:silverstripe:silverstripe:*:*:*:*:*:*:*:*"],"severity":"Medium"},"references":[{"type":"WEB","url":"https://www.silverstripe.org/download/security-releases/CVE-2020-6165"}],"affected":[{"package":{"name":"silverstripe","ecosystem":"Bitnami","purl":"pkg:bitnami/silverstripe"},"ranges":[{"type":"SEMVER","events":[{"introduced":"3.2.0"},{"fixed":"3.2.4"},{"introduced":"3.2.5"},{"fixed":"3.3.0"},{"introduced":"4.5.0"},{"fixed":"4.5.3"}]}],"database_specific":{"source":"https://github.com/bitnami/vulndb/tree/main/data/silverstripe/BIT-silverstripe-2020-6165.json"},"severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"}]}],"schema_version":"1.7.3"}