silverstripe/recipe-cms
Affected
- introduced
4.5.0, fixed4.5.3(ecosystem)
Fixed versions
4.5.3
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: BIT-silverstripe-2020-6165, CVE-2020-6165
Silverstripe has Incorrect Default Permissions
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.
Medium Basis: The source's own band: MODERATE
4.5.0, fixed 4.5.3 (ecosystem)4.5.3
The export has no generic command for this ecosystem.
3.2.0, fixed 3.2.4 (ecosystem)3.2.4
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0