Silverstripe Graphql vulnerabilities

7 known vulnerabilities affecting silverstripe/graphql.

Total CVEs

7

CISA KEV

0

Public exploits

0

Exploited in wild

0

Severity breakdown

HIGH3MEDIUM4

Vulnerabilities

Page 1 of 1

CVE-2023-44401MEDIUMCVSS 5.3≥ 4.0.0, < 4.3.7≥ 5.0.0, < 5.1.32024-01-23

CVE-2023-44401 [MEDIUM] CWE-863 View permissions are bypassed for paginated lists of ORM data View permissions are bypassed for paginated lists of ORM data ### Impact `canView` permission checks are bypassed for ORM data in paginated GraphQL query results where the total number of records is greater than the number of records per page. Note that this also affects GraphQL queries which have a limit applied, even if the query isn’t paginated per se. This has been fixed by ensuring no new record

CVE-2023-40180HIGHCVSS 7.5≥ 3.0.0, < 3.8.2≥ 4.0.0, < 4.1.3+3 more2023-10-17

CVE-2023-40180 [HIGH] CWE-400 Silverstripe GraphQL has DDOS Vulnerability due to lack of protection against recursive queries Silverstripe GraphQL has DDOS Vulnerability due to lack of protection against recursive queries ### Impact An attacker could use a recursive graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed graphql schemas. If your Silverstripe CMS project does not expose a public facing g

CVE-2023-28104HIGH≥ 4.1.1, < 4.1.2≥ 4.2.2, < 4.2.32023-03-16

CVE-2023-28104 [HIGH] CWE-770 DDOS attack on graphql endpoints DDOS attack on graphql endpoints An attacker could use a specially crafted graphql query to execute a Distributed Denial of Service attack (DDOS attack) against a website. This mostly affects websites with publicly exposed and particularly large/complex graphql schemas. If your Silverstripe CMS project does not expose a public facing graphql schema, a user account is required to trigger the DDOS attack. If your site is hosted behin

CVE-2019-12437HIGH≥ 2.0.0, < 2.0.5≥ 3.1.0, < 3.1.22022-05-24

CVE-2019-12437 [HIGH] CWE-352 Silverstripe CSRF Protection Bypass via GraphQL Silverstripe CSRF Protection Bypass via GraphQL In SilverStripe/GraphQL prior to 2.0.5 and 3.1.2, the previous fix for SS-2018-007 does not completely mitigate the risk of CSRF in GraphQL mutations.

CVE-2020-6165MEDIUM≥ 3.2.0, < 3.2.42022-05-24

CVE-2020-6165 [MEDIUM] CWE-276 Silverstripe has Incorrect Default Permissions 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 pe

CVE-2021-28661MEDIUM≥ 3.0.0, < 3.5.22021-10-12

CVE-2021-28661 [MEDIUM] CWE-863 SilverStripe GraphQL Server permission checker not inherited by query subclass. SilverStripe GraphQL Server permission checker not inherited by query subclass. Default SilverStripe GraphQL Server (aka silverstripe/graphql) 3.x through 3.4.1 permission checker not inherited by query subclass.

CVE-2020-26136MEDIUM≥ 3.0.0, < 3.5.0≥ 4.0.0-alpha1, < 4.0.0-alpha22021-06-10

CVE-2020-26136 [MEDIUM] CWE-287 Authentication bypass in SilverStripe GraphQL Authentication bypass in SilverStripe GraphQL The GraphQL module accepts basic-auth as an authentication method by default. This can be used to bypass MFA authentication if the silverstripe/mfa module is installed, which is now a commonly installed module. A users password is still required though. Basic-auth has been removed as a default authentication method. If desired, it can be re-enabled by adding it to the aut