# CVE-2023-40180: Denial of service vulnerability in silverstripe-graphql via recursive queries > Attackers can cause denial of service on Silverstripe websites via recursive GraphQL queries, particularly affecting sites with public schemas. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 Oct 2023 - **Updated:** 16 Sep 2024 - **Also known as:** GHSA-v23w-pppm-jh66 ## What is CVE-2023-40180? CVE-2023-40180 is a high-severity denial of service vulnerability in silverstripe-graphql, published on 16 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2023-40180? 10 open source packages ship an affected version, including silverstripe/graphql. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `silverstripe/graphql` | Packagist | From 3.0.0 | 3.8.2 | | `silverstripe/graphql` | Packagist | From 3.0.0 | 3.8.2 | | `silverstripe/graphql` | Packagist | From 4.0.0 | 4.1.3 | | `silverstripe/graphql` | Packagist | From 4.0.0 | 4.1.3 | | `silverstripe/graphql` | Packagist | From 4.2.0 | 4.2.5 | | `silverstripe/graphql` | Packagist | From 4.2.0 | 4.2.5 | | `silverstripe/graphql` | Packagist | From 4.3.0 | 4.3.4 | | `silverstripe/graphql` | Packagist | From 4.3.0 | 4.3.4 | | `silverstripe/graphql` | Packagist | From 5.0.0 | 5.0.3 | | `silverstripe/graphql` | Packagist | From 5.0.0 | 5.0.3 | Products: Silverstripe Graphql. ## How do I fix CVE-2023-40180? Upgrade silverstripe/graphql to a fixed version for your release line: 3.8.2, 4.1.3, 4.2.5 or 4.3.4. ## Is CVE-2023-40180 being exploited? There is no known exploitation of CVE-2023-40180 in the wild and no public exploit code. ## Other vulnerabilities in silverstripe-graphql - [CVE-2023-28104](https://insights.sbomify.com/CVE-2023-28104/): silverstripe/graphql Denial of Service vulnerability (high 7.5) - [CVE-2023-44401](https://insights.sbomify.com/CVE-2023-44401/): Silverstripe GraqhQL's view permissions are bypassed for paginated lists of ORM data (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-40180 and fix it if it is affected. What it is: CVE-2023-40180 is a high-severity denial of service vulnerability in silverstripe-graphql, published on 16 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-40180 in the wild and no public exploit code. Affected packages and fixed versions: - silverstripe/graphql (Packagist): affected from 3.0.0; fixed in 3.8.2 - silverstripe/graphql (Packagist): affected from 3.0.0; fixed in 3.8.2 - silverstripe/graphql (Packagist): affected from 4.0.0; fixed in 4.1.3 - silverstripe/graphql (Packagist): affected from 4.0.0; fixed in 4.1.3 - silverstripe/graphql (Packagist): affected from 4.2.0; fixed in 4.2.5 - silverstripe/graphql (Packagist): affected from 4.2.0; fixed in 4.2.5 - silverstripe/graphql (Packagist): affected from 4.3.0; fixed in 4.3.4 - silverstripe/graphql (Packagist): affected from 4.3.0; fixed in 4.3.4 - silverstripe/graphql (Packagist): affected from 5.0.0; fixed in 5.0.3 - silverstripe/graphql (Packagist): affected from 5.0.0; fixed in 5.0.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-40180/ (Markdown: https://insights.sbomify.com/CVE-2023-40180/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-40180 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-40180 - OSV: https://osv.dev/vulnerability/CVE-2023-40180 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-40180/ Summaries are generated and may contain mistakes; the official description above is the record.