Headline
GHSA-67g8-c724-8mp3: 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 behind a content delivery network (CDN), such as Imperva or CloudFlare, this will likely further mitigate the risk.
Upgrade to silverstripe/graphql 4.2.3 or 4.1.2 or above to remedy the vulnerability.
Package
composer silverstripe/graphql (Composer)
Affected versions
>= 4.1.1, < 4.1.2
>= 4.2.2, < 4.2.3
Patched versions
4.1.2
4.2.3
Description
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 behind a content delivery network (CDN), such as Imperva or CloudFlare, this will likely further mitigate the risk.
Upgrade to silverstripe/graphql 4.2.3 or 4.1.2 or above to remedy the vulnerability.
References
- GHSA-67g8-c724-8mp3
- https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/graphql/CVE-2023-28104.yaml
- https://www.silverstripe.org/download/security-releases/CVE-2023-28104
GuySartorelli published to silverstripe/silverstripe-graphql
Mar 15, 2023
Published to the GitHub Advisory Database
Mar 16, 2023
Reviewed
Mar 16, 2023
Last updated
Mar 16, 2023
Related news
`silverstripe/graphql` serves Silverstripe data as GraphQL representations. In versions 4.2.2 and 4.1.1, an attacker could use a specially crafted graphql query to execute a denial of service attack against a website which has a publicly exposed graphql endpoint. This mostly affects websites with particularly large/complex graphql schemas. Users should upgrade to `silverstripe/graphql` 4.2.3 or 4.1.2 to remedy the vulnerability.