GHSA-3h96-34p3-xm76 json
GraphQL-Ruby's Ruby lexer does not count comment tokens for the purposes of max_query_string_tokens
published 6mo ago modified 6mo ago
- cvss
- 5.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
GraphQL-Ruby's `max_query_string_tokens` configuration didn't count comment tokens against the limit, allowing strings to be processed even after the configured maximum had actually been reached.
In patched versions, the Ruby lexer does count these tokens.
GraphQL-CParser is not affected by this problem.
`max_query_string_tokens` was introduced in v2.3.1. Each 2.x version has received a new patch release for including a fix.
Patch / fix
- rubygems graphql 2.3.23, 2.4.18, 2.5.26, 2.6.1
Is GHSA-3h96-34p3-xm76 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | graphql | >=2.6.0, <2.6.1 >=2.5.0, <2.5.26 >=2.4.0, <2.4.18 >=2.3.1, <2.3.23 |
2.6.1 2.5.26 2.4.18 2.3.23 |
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
Sources
- GitHub Advisory GHSA-3h96-34p3-xm76
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.