CVE-2020-6165

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.

• CVE ID
• CVE-2020-6165

• Assigner
• cve@mitre.org

• Vulnerability Status
• Analyzed

• Published Version
• 2020-07-15T21:15:13

• Last Modified Date
• 2020-07-23T14:22:48

• Version
• 2.0

• Vector String
• AV:N/AC:L/Au:N/C:P/I:N/A:N

• Access Vector
• NETWORK

• Access Compatibility
• LOW

• Authentication
• NONE

• Confidentiality Impact
• PARTIAL

• Integrity Impact
• NONE

• Availability Impact
• NONE

• Base Score
• 5

• Severity
• MEDIUM

• Exploitability Score
• 10

• Impact Score
• 2.9

• Version
• 3.1

• Vector String
• CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

• Attack Vector
• NETWORK

• Attack Compatibility
• LOW

• Privileges Required
• NONE

• User Interaction
• NONE

• Scope
• UNCHANGED

• Confidentiality Impact
• LOW

• Availability Impact
• NONE

• Base Score
• 5.3

• Base Severity
• MEDIUM

• Exploitability Score
• 3.9

• Impact Score
• 1.4