cve.bz

CVE-2023-50730 typelevel grackle: Uncontrolled Resource Consumption

7.5 highEPSS 0.8%Fix available

High (7.5) in typelevel grackle. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in org.typelevel:grackle-core_2.13 0.18.0.

On this page
Grackle is a GraphQL server written in functional Scala, built on the Typelevel stack. The GraphQL specification requires that GraphQL fragments must not form cycles, either directly or indirectly. Prior to Grackle version 0.18.0, that requirement wasn't checked, and queries with cyclic fragments would have been accepted for type checking and compilation. The attempted compilation of such fragments would result in a JVM `StackOverflowError` being thrown. Some knowledge of an applications GraphQL schema would be required to construct such a query, however no knowledge of any application-specific performance or other behavioural characteristics would be needed. Grackle uses the cats-parse library for parsing GraphQL queries. Prior to version 0.18.0, Grackle made use of the cats-parse `recursive` operator. However, `recursive` is not currently stack safe. `recursive` was used in three places in the parser: nested selection sets, nested input values (lists and objects), and nested list type declarations. Consequently, queries with deeply nested selection sets, input values or list types could be constructed which exploited this, causing a JVM `StackOverflowException` to be thrown during parsing. Because this happens very early in query processing, no specific knowledge of an applications GraphQL schema would be required to construct such a query. The possibility of small queries resulting in stack overflow is a potential denial of service vulnerability. This potentially affects all applications using Grackle which have untrusted users. Both stack overflow issues have been resolved in the v0.18.0 release of Grackle. As a workaround, users could interpose a sanitizing layer in between untrusted input and Grackle query processing.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-50730 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-50730?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-50730?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-50730 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
typelevel:gracklebefore 0.18.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-g56x-7j6w-g8r8Mavenorg.typelevel:grackle-core_2.13<0.18.00.18.0
GHSA-g56x-7j6w-g8r8Mavenorg.typelevel:grackle-core_3<0.18.00.18.0
GHSA-g56x-7j6w-g8r8Mavenorg.typelevel:grackle-core_sjs1_2.13<0.18.00.18.0
GHSA-g56x-7j6w-g8r8Mavenorg.typelevel:grackle-core_sjs1_3<0.18.00.18.0
GHSA-g56x-7j6w-g8r8Mavenorg.typelevel:grackle-core_native0.4_2.13<0.18.00.18.0
GHSA-g56x-7j6w-g8r8Mavenorg.typelevel:grackle-core_native0.4_3<0.18.00.18.0
GHSA-g56x-7j6w-g8r8Mavenedu.gemini:gsp-graphql-core_2.13<=0.14.0no fix published
GHSA-g56x-7j6w-g8r8Mavenedu.gemini:gsp-graphql-core_3<=0.14.0no fix published
GHSA-g56x-7j6w-g8r8Mavenedu.gemini:gsp-graphql-core_sjs1_2.13<=0.14.0no fix published
GHSA-g56x-7j6w-g8r8Mavenedu.gemini:gsp-graphql-core_sjs1_3<=0.14.0no fix published
GHSA-g56x-7j6w-g8r8Mavenedu.gemini:gsp-graphql-core_native0.4_2.13<=0.14.0no fix published
GHSA-g56x-7j6w-g8r8Mavenedu.gemini:gsp-graphql-core_native0.4_3<=0.14.0no fix published

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON