CyberSecBulletin
CVE-2023-40180NVD status: Modified

silverstripe-graphql: Uncontrolled Resource Consumption

CVE-2023-40180 is a high-severity uncontrolled resource consumption vulnerability in silverstripe-graphql from Silverstripe, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected silverstripe-graphql versions: >= 3.0.0, < 3.8.2; >= 4.0.0, < 4.1.3; >= 4.2.0, < 4.2.5, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.13% chance of exploitation within 30 days, higher than 67% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Graphql to 3.8.2 or 4.1.3 or 4.2.5 or 4.3.4, whichever matches your release line, or a later version.
  2. Read the advisory on github.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Silverstripesilverstripe-graphql>= 3.0.0, < 3.8.2; >= 4.0.0, < 4.1.3; >= 4.2.0, < 4.2.5; >= 4.3.0, < 4.3.4; >= 5.0.0, < 5.0.3Not stated
SilverstripeGraphql3.0.0 up to, but not including, 3.8.2; 4.0.0 up to, but not including, 4.1.3; 4.2.0 up to, but not including, 4.2.5; 4.3.0 up to, but not including, 4.3.4; 5.0.0 up to, but not including, 5.0.33.8.2, 4.1.3, 4.2.5, 4.3.4, 5.0.3

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighCNA (github.com)
CVSS 3.17.5HighNVD

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How developers prevent this class of flaw

  • Ensure that protocols have specific limits of scale placed on them.
  • Ensure that all failures in resource allocation place the system into a safe posture.

More Uncontrolled Resource Consumption vulnerabilities (CWE-400)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other vulnerabilities in silverstripe-graphql

All silverstripe-graphql vulnerabilities

Recent Uncontrolled Resource Consumption vulnerabilities

Spotted an error? Tell us.