BIT-silverstripe-2020-6165

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/silverstripe/BIT-silverstripe-2020-6165.json
JSON Data
https://api.test.osv.dev/v1/vulns/BIT-silverstripe-2020-6165
Aliases
Published
2024-03-06T11:06:12.375Z
Modified
2024-03-06T11:25:28.861Z
Summary
[none]
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.

Database specific
{
    "cpes": [
        "cpe:2.3:a:silverstripe:silverstripe:*:*:*:*:*:*:*:*"
    ],
    "severity": "Medium"
}
References

Affected packages

Bitnami / silverstripe

Package

Name
silverstripe
Purl
pkg:bitnami/silverstripe

Severity

  • 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N CVSS Calculator

Affected 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