graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 Denial of Service via Parser max_tokens Comment Runs
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| graphql-python | graphql-core | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 contains a denial of service vulnerability that allows unauthenticated attackers to bypass the parser max_tokens limit using long runs of comments. Attackers can submit GraphQL documents of consecutive comments that Lexer.lookahead fully tokenizes before limit checks, consuming CPU and memory proportional to document size. | |
| Title | graphql-core 3.2.12 before 3.2.14 and 3.3.0rc1 before 3.3.2 Denial of Service via Parser max_tokens Comment Runs | |
| First Time appeared |
Graphql
Graphql graphql |
|
| Weaknesses | CWE-770 | |
| CPEs | cpe:2.3:a:graphql:graphql:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Graphql
Graphql graphql |
|
| References |
|
|
| Metrics |
cvssV3_1
|
No data.
No data.
No data.
No data.