CVE-2023-28867: GraphQL Java vulnerable to stack consumption
7.5
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.27144%
CWE
Published
3/27/2023
Updated
4/3/2023
KEV Status
No
Technology
Java
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| com.graphql-java:graphql-java | maven | < 0.0.0-2023-03-20T01-49-44-80e3135 | 0.0.0-2023-03-20T01-49-44-80e3135 |
| com.graphql-java:graphql-java | maven | >= 1.2, < 17.5 | 17.5 |
| com.graphql-java:graphql-java | maven | >= 18.0, < 18.4 | 18.4 |
| com.graphql-java:graphql-java | maven | >= 19.0, < 19.4 | 19.4 |
| com.graphql-java:graphql-java | maven | = 20.0 | 20.1 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from recursive parsing logic without depth limits. The key evidence comes from:- 1) The fix in PR #3112 explicitly adds depth tracking and limits to the parser- 2) CWE-770 classification indicates unbounded resource allocation (stack space in this case)- 3) Multiple patched versions across different branches all mention 'preventing stack overflow via depth limiting'- 4) The ANTLR recursive descent parser architecture mentioned in the PR discussion is inherently stack-based- While specific function names aren't listed in the advisory, the parser entry point (parseDocument) and grammar rules are the logical location for this vulnerability based on the patch description and stack consumption nature.