Keystone: `graphql.maxTake` bypass with negative `take`
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| keystonejs | keystone | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Keystonejs | Keystone |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cqmq-8755-7xvh | Keystone vulnerable to `graphql.maxTake` bypass with negative `take` |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.670% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Keystonejs
Keystonejs keystone |
|
| Vendors & Products |
Keystonejs
Keystonejs keystone |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Keystone is a content management system for Node.js. Prior to 6.5.3, the findMany resolver in packages/core/src/lib/core/queries/resolvers.ts compares the signed take argument directly with graphql.maxTake, allowing a remote unauthenticated GraphQL client to provide a negative take value whose magnitude exceeds the configured bound. The bypass also applies to relationship queries and can return more records than the developer intended, potentially exhausting service resources. This issue is fixed in version 6.5.3. | |
| Title | Keystone: `graphql.maxTake` bypass with negative `take` | |
| Weaknesses | CWE-20 CWE-480 |
|
| References |
| |
| Metrics |
cvssV3_1
|