CVE-2023-50730

CVE-2023-50730 is a high-severity uncontrolled resource consumption vulnerability in org.typelevel:grackle-core_2.13 (maven), affecting versions < 0.18.0. It is fixed in 0.18.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Grackle has StackOverflowError in GraphQL query processing

Workarounds

Users could interpose a sanitizing layer in between untrusted input and Grackle query processing.

Impact

Prior to this fix, the GraphQL query parsing was vulnerable to StackOverflowErrors. 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.

[!CAUTION]
No specific knowledge of an application's GraphQL schema would be required to construct a pathological query.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2023-50730 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.18.0); upgrading removes the vulnerable code path.

Affected versions

org.typelevel:grackle-core_2.13 (< 0.18.0) org.typelevel:grackle-core_3 (< 0.18.0) org.typelevel:grackle-core_sjs1_2.13 (< 0.18.0) org.typelevel:grackle-core_sjs1_3 (< 0.18.0) org.typelevel:grackle-core_native0.4_2.13 (< 0.18.0) org.typelevel:grackle-core_native0.4_3 (< 0.18.0) edu.gemini:gsp-graphql-core_2.13 (<= 0.14.0) edu.gemini:gsp-graphql-core_3 (<= 0.14.0) edu.gemini:gsp-graphql-core_sjs1_2.13 (<= 0.14.0) edu.gemini:gsp-graphql-core_sjs1_3 (<= 0.14.0) edu.gemini:gsp-graphql-core_native0.4_2.13 (<= 0.14.0) edu.gemini:gsp-graphql-core_native0.4_3 (<= 0.14.0)

Security releases

org.typelevel:grackle-core_2.13 → 0.18.0 (maven) org.typelevel:grackle-core_3 → 0.18.0 (maven) org.typelevel:grackle-core_sjs1_2.13 → 0.18.0 (maven) org.typelevel:grackle-core_sjs1_3 → 0.18.0 (maven) org.typelevel:grackle-core_native0.4_2.13 → 0.18.0 (maven) org.typelevel:grackle-core_native0.4_3 → 0.18.0 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

The stack overflow issues have been resolved in the v0.18.0 release of Grackle.

Frequently Asked Questions

  1. What is CVE-2023-50730? CVE-2023-50730 is a high-severity uncontrolled resource consumption vulnerability in org.typelevel:grackle-core_2.13 (maven), affecting versions < 0.18.0. It is fixed in 0.18.0. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
  2. How severe is CVE-2023-50730? CVE-2023-50730 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2023-50730?
    • org.typelevel:grackle-core_2.13 (maven) (versions < 0.18.0)
    • org.typelevel:grackle-core_3 (maven) (versions < 0.18.0)
    • org.typelevel:grackle-core_sjs1_2.13 (maven) (versions < 0.18.0)
    • org.typelevel:grackle-core_sjs1_3 (maven) (versions < 0.18.0)
    • org.typelevel:grackle-core_native0.4_2.13 (maven) (versions < 0.18.0)
    • org.typelevel:grackle-core_native0.4_3 (maven) (versions < 0.18.0)
    • edu.gemini:gsp-graphql-core_2.13 (maven) (versions <= 0.14.0)
    • edu.gemini:gsp-graphql-core_3 (maven) (versions <= 0.14.0)
    • edu.gemini:gsp-graphql-core_sjs1_2.13 (maven) (versions <= 0.14.0)
    • edu.gemini:gsp-graphql-core_sjs1_3 (maven) (versions <= 0.14.0)
    • edu.gemini:gsp-graphql-core_native0.4_2.13 (maven) (versions <= 0.14.0)
    • edu.gemini:gsp-graphql-core_native0.4_3 (maven) (versions <= 0.14.0)
  4. Is there a fix for CVE-2023-50730? Yes. CVE-2023-50730 is fixed in 0.18.0. Upgrade to this version or later.
  5. Is CVE-2023-50730 exploitable, and should I be worried? Whether CVE-2023-50730 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2023-50730 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2023-50730?
    • Upgrade org.typelevel:grackle-core_2.13 to 0.18.0 or later
    • Upgrade org.typelevel:grackle-core_3 to 0.18.0 or later
    • Upgrade org.typelevel:grackle-core_sjs1_2.13 to 0.18.0 or later
    • Upgrade org.typelevel:grackle-core_sjs1_3 to 0.18.0 or later
    • Upgrade org.typelevel:grackle-core_native0.4_2.13 to 0.18.0 or later
    • Upgrade org.typelevel:grackle-core_native0.4_3 to 0.18.0 or later

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo